Called exploited 1 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE reserved
- CVE published8d
- First KEV listing1d
- Last sighting3d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Sep 11, 2026
- EUVDENISA, European Unionlisted Sep 11, 2026
- VulnCheck KEVcommercial researchlisted Sep 11, 2026
- CIRCLaggregator, mirrors the abovelisted Sep 11, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.rapid7.com/blog/post/etr-cve-2026-85706-critical-gitlab-
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationx.com/watchtowrcyber/status/2098361659941126333
3 public reports collected from VulnCheck and CIRCL, first on Sep 11, 2026. Each links to its original source. We have not verified them.
Description
GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
Required action (CISA)
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.
