Skip to main content
ExploitedIn CISA KEVFix available

CVE-2026-85706

Exploitation confirmed. First attested on 2026-09-11 by CISA-ADP, CISA KEV, GCVE · previdian, GCVE · shadowserver.

  • Published2026-09-12
  • Fixed in19.3.2 · 19.2.6 · 19.1.8 · 19.0.9 · 18.11.12
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 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.

Timeline

dates in UTC
  1. 2026-09-11Added to the CISA KEV catalogCISA KEV
  2. 2026-09-11Listed as exploited by GCVEGCVE
  3. 2026-09-11Exploitation first reportedCISA KEV
  4. 2026-09-1203:16CVE publishedNVD
  5. 2026-09-1203:55SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-10-27 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-85706?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-85706?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
GitLab
BranchAffectedFixed in
19.3≥ 19.3.0, < 19.3.219.3.2
19.2≥ 19.2.0, < 19.2.619.2.6
19.1≥ 19.1.0, < 19.1.819.1.8
19.0≥ 19.0.0, < 19.0.919.0.9
18.x≥ 18.7.0, < 18.11.1218.11.12

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update GitLab to 19.3.2 · 19.2.6 · 19.1.8 · 19.0.9 · 18.11.12
  2. CISA’s required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.due 2026-09-14

Detection

read 2026-10-27 00:21 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
13 repositories, unverifiedFlowerWitch/CVE-2026-85706_docker_expguneykabel/cve-2026-85706solivaquaant/CVE-2026-85706ynsmroztas/GitLabSniperjithinkrishnanrs/gitlab-cve-2026-85706-ioc
PoC-in-GitHub

CISA Known Exploited Vulnerability

Date Added
2026-09-11
Patch Due Date
2026-09-14
Ransomware Use
Unknown
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Sources

  • NVDCVE recordread 2026-10-23
  • CISA KEVKEV entry2026-09-11
  • GCVEexploitation2026-09-11
  • CISA-ADPSSVC decisionactive2026-09-12
  • OpenCVESSVC decisionactive—
  • CNACVSS 3.110read 2026-10-23
  • CNAweakness (CWE)CWE-22read 2026-10-23
  • FIRST EPSSEPSS score97.4 %read 2026-10-27
  • PoC-in-GitHubproof of concept13read 2026-10-27
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Published
2026-09-12
Last Modified
2026-09-24
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-85706?

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 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.

Is CVE-2026-85706 actively exploited?

Yes. CVE-2026-85706 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-09-14.

What is the CVSS score for CVE-2026-85706?

CVE-2026-85706 has a CVSS v3 base score of 10 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.

Running GitLab? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, September 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database