CVE-2025-12575: Server-Side Request Forgery (SSRF) in GitLab
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: GitLab GitLab 18.6.6, 18.7.4, 18.8.4.
Low priority for now. Upgrade to GitLab GitLab 18.6.6, 18.7.4, 18.8.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
GitLab has remediated an issue in GitLab EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user with certain permissions to make unauthorized requests to internal network services through the GitLab server.
- Published
- Feb 11, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-918
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitLab
- 5.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gitlab | gitlab | cpe:2.3:a:gitlab:gitlab |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.
GitLab GitLab
- 18.0 and later · before 18.6.6affected · semver
- 18.7 and later · before 18.7.4affected · semver
- 18.8 and later · before 18.8.4affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gitlab gitlab18.0.0 and later · before 18.6.6
- gitlab gitlab18.7.0 and later · before 18.7.4
- gitlab gitlab18.8.0 and later · before 18.8.4
Same product
gitlab: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV100Now
- CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV99Now
- CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV97Now
Published before and after this one in the same product
- ← EarlierCVE-2026-1751Feb 2, 2026 · Missing Authorization in GitLab12Monitor
- ← EarlierCVE-2025-12073Feb 11, 2026 · Server-Side Request Forgery (SSRF) in GitLab17Monitor
- Later →CVE-2025-14560Feb 11, 2026 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitLab GitLab | 18.6.6 | Vendor (CNA) |
| GitLab GitLab | 18.7.4 | Vendor (CNA) |
| GitLab GitLab | 18.8.4 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- go7f0qhofinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-75871197 days apartServer-Side Request Forgery (SSRF) in GitLab AI Gateway38Monitor
- CVE-2025-6454152 days apartServer-Side Request Forgery (SSRF) in GitLab35Monitor
- CVE-2024-8977489 days apartServer-Side Request Forgery (SSRF) in GitLab32Monitor
- CVE-2026-9204120 days apartServer-Side Request Forgery (SSRF) in GitLab26Monitor
- CVE-2024-8635517 days apartServer-Side Request Forgery (SSRF) in GitLab26Monitor
- CVE-2025-120730 days apartServer-Side Request Forgery (SSRF) in GitLab17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2025-1198462 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab27Monitor
- CVE-2025-1265377 days apartAuthentication Bypass by Spoofing in GitLab26Monitor
- CVE-2026-174714 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab17Monitor
- CVE-2026-060228 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab17Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.