02 Records
FEED: ACQUIRING
01 RecordSTATE: PUBLISHED
02 Description
CNA: GitLabServer-Side Request Forgery (SSRF) in eScriptorium
03 Exploitation and scoring
SRC: CISA, FIRST, NVD, RED HAT- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
CISA publishes the decision points, not a final SSVC decision. The decision also depends on mission and well-being impact, which is a property of your deployment rather than of the vulnerability.- EPSS probability
- 0.22% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Ranks above 12.6% of scored records. A rank, not a probability.
- NVD base score
- 8.5 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- NVD analysis status
- Analyzed. NVD last modified this record on 2026-08-18.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
SCHEMA: 5.2
- Published
- 2026-08-06 15:11Z29 DAYS AGO
- Last updated
- 2026-08-06 15:46Z29 DAYS AGO
- Reserved
- 2026-07-30
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- High (CVSS 8.5)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- Weaknesses
- CWE-918Server-Side Request Forgery (SSRF)Base
- Data version
- 5.2
- Document digest
- 4cf1c1b1721677df154c3bb27d62c668121f6b4c8908be99ab9d5afb1d7cc4fc
05 Affected products
PAIRS: 1VendorProductVersionsPlatforms
SRC: CNA
Upgrade to fixed version: 26.04.2, 1.0.1 or 0.13.9. As a mitigation on affected versions, set the IMPORT_ALLOWED_DOMAINS setting to an explicit list of permitted domains instead of leaving it at its default value of '*'.