Server-Side Request Forgery (SSRF) in GitLab
Noroxi assessment
Priority: Monitor (action score 32/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.55% (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 17.2.9, 17.3.5, 17.4.2.
Low priority for now. Upgrade to GitLab GitLab 17.2.9, 17.3.5, 17.4.2 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
An issue has been discovered in GitLab EE affecting all versions starting from 15.10 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. Instances with Product Analytics Dashboard configured and enabled could be vulnerable to SSRF attacks.
- Published
- Oct 10, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-918
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.1
- CNA · GitLab
- 8.2
- 0.1 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gitlab gitlab15.10 and later · before 17.2.9
- gitlab gitlab17.3.0 and later · before 17.3.5
- gitlab gitlab17.4.0 and later · before 17.4.2
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
- 15.10 and later · before 17.2.9affected · semver
- 17.3 and later · before 17.3.5affected · semver
- 17.4 and later · before 17.4.2affected · semver
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 GitLabKEV98Now
- CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV97Now
Published before and after this one in the same product
- ← EarlierCVE-2024-8974Sep 26, 2024 · Incorrect Provision of Specified Functionality in GitLab17Monitor
- ← EarlierCVE-2023-3441Oct 1, 2024 · Exposure of Sensitive Information Due to Incompatible Policies in GitLab36Monitor
- Later →CVE-2024-9596Oct 10, 2024 · Inclusion of Sensitive Information in Source Code 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 | 17.2.9 | Vendor (CNA) |
| GitLab GitLab | 17.3.5 | Vendor (CNA) |
| GitLab GitLab | 17.4.2 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-6454337 days apartServer-Side Request Forgery (SSRF) in GitLab35Monitor
- CVE-2024-863528 days apartServer-Side Request Forgery (SSRF) in GitLab26Monitor
- CVE-2025-12575489 days apartServer-Side Request Forgery (SSRF) in GitLab21Monitor
- CVE-2023-6195112 days apartServer-Side Request Forgery (SSRF) in GitLab17Monitor
- CVE-2025-12073489 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-2024-667828 days apartAuthentication Bypass by Spoofing in GitLab36Monitor
- CVE-2024-91641 days apartMissing Authentication for Critical Function in GitLab35Monitor
- CVE-2024-1166847 days apartInsufficient Session Expiration in GitLab21Monitor
- CVE-2023-511776 days apartExposure of Sensitive Information Due to Incompatible Policies in GitLab14Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- 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:H/I:H/A:N
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.