GitLab unauth commits API file read (CISA KEV)
Direct answer
GitLab unauth commits API file read (CISA KEV), also tracked as CVE-2026-85706 / GitLab commits API path traversal is a critical-severity threat campaign HOL Guard tracked from Sep 11, 2026 to Sep 11, 2026, verified against 4 primary sources and last reviewed Sep 20, 2026. Active tracking has ended and the record remains published as a permanent historical research record.
Self-managed GitLab CE/EE in affected 18.7–19.3 trains had improper path confinement on the commits API so that, under certain conditions, an unauthenticated user could read arbitrary files from the GitLab server. CISA added it to KEV. Upgrade to 19.1.8, 19.2.6, or 19.3.2.
Also tracked as CVE-2026-85706 · GitLab commits API path traversal
- First observed
- Sep 11, 2026
- Last observed
- Sep 11, 2026
- Last reviewed
- Sep 20, 2026
- Tracking ended
- Sep 11, 2026
Record exports
Uncertainty and limitations
Read the evidence limits before acting on this record.
Exact trigger conditions are described in GitLab's advisory; confirm your minor train before choosing 19.1.8 vs 19.2.6 vs 19.3.2.
- Affects GitLab CE/EE from 18.7 before the listed fixed minors.
- CISA KEV listing elevates urgency; this campaign does not invent exploit tooling details.
- Path traversal file read is the scoped impact — not claimed RCE unless a separate advisory says so.
Guard coverage and policy
What Guard's reviewed assertions do and do not claim for this campaign, and the reviewed starting points for defense.
No Guard coverage mapping or campaign-specific policy guidance is published for this record.
Safe next step. Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.
Timeline
Reviewed events, oldest first, each tied to a verified source.
- Disclosure
GitLab remediated CVE-2026-85706 for commits API path traversal on self-managed instances.
- Update
CISA listed CVE-2026-85706 in the Known Exploited Vulnerabilities catalog.
Source:CISA KEV catalog entry
Publication clock: 234.9 hours from reviewed disclosure timestamp to HOL publication; 12-hour critical target; historical backfill outside target.
Reviewed artifacts
The specific artifacts this record concerns, as reviewed. Names and versions are shown as text; a registry link is not recorded here.
GitLab CE/EE@>=18.7 <19.1.8 || >=19.2 <19.2.6 || >=19.3 <19.3.2gitlabpackage
Sources
Every claim on this record is traceable to the sources below.
Campaign questions, answered
Self-managed GitLab CE/EE in affected 3 trains had improper path confinement on the commits API so that, under certain conditions, an unauthenticated user could read arbitrary files from the GitLab server. HOL Guard tracked the campaign from Sep 11, 2026 to Sep 11, 2026.
No. Active tracking ended Sep 11, 2026; this page remains as a labeled historical research record and does not imply the threat is currently active.
The record cites 4 primary sources, names 1 reviewed artifact, and was last fully reviewed Sep 20, 2026 by HOL Guard Security Publishing. Its uncertainty and limitations are stated on the record itself.
Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.
The permalink above is permanent. The full record can be downloaded from this page as JSON, an artifact CSV, and a STIX 2.1 bundle, and corrections can be requested through the published correction path on the record. Exact trigger conditions are described in GitLab's advisory; confirm your minor train before choosing 19.1.8 vs 19.2.6 vs 19.3.2.
Reviewed in full by HOL Guard Security Publishing.
- Published
- Last full review
- Last modified
Record HGTC-2026-7CE1D780