Authentication Bypass Using an Alternate Path or Channel in GitLab
Noroxi assessment
Priority: Monitor (action score 17/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.25% (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.7.6, 18.8.6, 18.9.2.
Low priority for now. Upgrade to GitLab GitLab 18.7.6, 18.8.6, 18.9.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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.6 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to disclose metadata from private issues, merge requests, epics, milestones, or commits due to improper filtering in the snippet rendering process under certain circumstances.
- Published
- Mar 11, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-288
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitLab
- 4.3
- 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.
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.6.0 and later · before 18.7.6
- gitlab gitlab18.8.0 and later · before 18.8.6
- gitlab gitlab18.9.0 and later · before 18.9.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.6 and later · before 18.7.6affected · semver
- 18.8 and later · before 18.8.6affected · semver
- 18.9 and later · before 18.9.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-2025-13929Mar 11, 2026 · Allocation of Resources Without Limits or Throttling in GitLab30Monitor
- ← EarlierCVE-2025-14513Mar 11, 2026 · Improper Validation of Specified Quantity in Input in GitLab30Monitor
- Later →CVE-2026-1069Mar 11, 2026 · Uncontrolled Recursion in GitLab30Monitor
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.7.6 | Vendor (CNA) |
| GitLab GitLab | 18.8.6 | Vendor (CNA) |
| GitLab GitLab | 18.9.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-2026-274514 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab32Monitor
- CVE-2025-1198490 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab27Monitor
- CVE-2025-0549306 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab27Monitor
- CVE-2026-452464 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab26Monitor
- CVE-2026-3035168 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab22Monitor
- CVE-2026-174714 days apartAuthentication Bypass Using an Alternate Path or Channel 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-2026-151628 days apartImproper Control of Generation of Code ('Code Injection') in GitLab22Monitor
- CVE-2026-297314 days apartImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab21Monitor
- CVE-2025-1257528 days apartServer-Side Request Forgery (SSRF) in GitLab21Monitor
- CVE-2025-1207328 days apartServer-Side Request Forgery (SSRF) in GitLab17Monitor
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
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-288 · Authentication Bypass Using an Alternate Path or ChannelCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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)
Change log
- 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.