Authentication Bypass by Assumed-Immutable Data in GitLab
Noroxi assessment
Priority: Monitor (action score 39/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: 14.7% (FIRST EPSS); higher than 96.6% of all records.
- 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 16.10.4, 16.11.1, 16.9.6.
Low priority for now. Upgrade to GitLab GitLab 16.10.4, 16.11.1, 16.9.6 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 CE/EE affecting all versions starting from 7.8 before 16.9.6, all versions starting from 16.10 before 16.10.4, all versions starting from 16.11 before 16.11.1. Under certain conditions, an attacker with their Bitbucket account credentials may be able to take over a GitLab account linked to another user's Bitbucket account, if Bitbucket is used as an OAuth 2.0 provider on GitLab.
- Published
- Apr 25, 2024
- Updated
- Jun 17, 2026
- EPSS
- 14.7% · 96th percentile
- CWE
- CWE-302
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · GitLab
- 7.3
- 1.5 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/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 gitlab7.8.0 and later · before 16.9.6
- gitlab gitlab16.10.0 and later · before 16.10.4
- gitlab gitlab16.11.0
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
- 7.8 and later · before 16.9.6affected · semver
- 16.10 and later · before 16.10.4affected · semver
- 16.11 and later · before 16.11.1affected · 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-2829Apr 25, 2024 · Inefficient Regular Expression Complexity in GitLab38Monitor
- ← EarlierCVE-2024-4006Apr 25, 2024 · Incorrect Authorization in GitLab17Monitor
- Later →CVE-2023-6682May 14, 2024 · Inefficient Regular Expression Complexity in GitLab26Monitor
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 | 16.10.4 | Vendor (CNA) |
| GitLab GitLab | 16.11.1 | Vendor (CNA) |
| GitLab GitLab | 16.9.6 | 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.
—
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-040291 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab40Plan
- CVE-2024-24340 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab39Monitor
- CVE-2024-7110119 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab25Monitor
- CVE-2024-704790 days apartImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab21Monitor
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
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-302 · Authentication Bypass by Assumed-Immutable DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- HTTP Verb TamperingCAPEC-274Medium
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Manipulating User-Controlled VariablesCAPEC-77likelihood: High · Very High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →