Skip to main content

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that,… (CVE-2026-85706)

0
Critical
Published: 09/12/2026 (09/12/2026, 03:30:22 UTC)
Source: GCVE Database

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.

CVSS v3.1

Score 10.0critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected software

gitlab
pkg:gem/gitlab
Affected versions
>=18.7 <19.1.8>=19.2 <19.2.6>=19.3 <19.3.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/13/2026, 00:40:31 UTC

Technical Analysis

CVE-2026-85706 is a critical security flaw in GitLab Community and Enterprise Editions affecting versions from 18.7 up to but not including 19.1.8, 19.2 up to but not including 19.2.6, and 19.3 up to but not including 19.3.2. The vulnerability arises from improper path confinement and lack of authentication enforcement in the repository commits API, enabling unauthenticated attackers to read arbitrary files on the server under certain conditions.

Potential Impact

An unauthenticated attacker can read arbitrary files on the GitLab server, potentially exposing sensitive information. The vulnerability has a CVSS 3.1 base score of 10.0, indicating critical severity with high confidentiality and integrity impact but no availability impact. This could lead to significant data exposure and compromise of system confidentiality and integrity.

Mitigation Recommendations

GitLab has remediated this issue in versions 19.1.8, 19.2.6, and 19.3.2 and later. Users should upgrade affected GitLab CE/EE instances to these fixed versions or later to mitigate this vulnerability. No additional mitigations are specified.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-f47w-mrg9-g9p2
Osv Schema Version
1.4.0
Aliases
["CVE-2026-85706"]
Database Specific Severity
CRITICAL
Cvss Version
3.1

Threat ID: 6aa5f00355bf5e2cf5ef7cd3

Added to database: 09/13/2026, 00:36:19 UTC

Last enriched: 09/13/2026, 00:40:31 UTC

Last updated: 09/13/2026, 03:19:41 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses