cyfenced.com →

[ CVE-2026-85706 · Published 12 Sep 2026 ]

Unauthenticated file read in GitLab through the commits API

Exploited · CISA KEV CVSS 10.0 EPSS 92%1 agency advisoryFix available

[ Why it matters ]Priority signals

  • Exploited in the wild: on CISA's Known Exploited Vulnerabilities list since 2026-09-11
  • EPSS: 92% chance of exploitation in the next 30 days (higher than 100% of CVEs)
  • Critical severity: CVSS 10.0

[ Analyst view ]Is this a red alert for you?

Red alert

CISA lists it as exploited, it needs no credentials and it can expose the secrets that protect your code and pipelines.

Red alert if
You run self-managed GitLab 18.7 or later on an unpatched release and it is reachable from the internet.
Can wait if
You use GitLab.com, or your self-managed GitLab is on a fixed release.
What it is
Missing authentication and improper path confinement in the GitLab repository commits API let an unauthenticated user read arbitrary files from the GitLab server under certain conditions. GitLab CE and EE 18.7 to 19.3 are affected; fixed releases are 18.11.12, 19.0.9, 19.1.8, 19.2.6 and 19.3.2.
Impact
Anyone who can reach your GitLab server can read files from it without an account. GitLab servers hold source code, configuration with secrets and the keys and tokens used by CI/CD pipelines, which can give an attacker access to your code, your build systems and the environments you deploy to.

How an attack would work MITRE ATT&CK

  1. T1190 Exploit Public-Facing ApplicationThe attacker sends crafted requests to the commits API of a GitLab server on the internet.
  2. T1552 Unsecured CredentialsConfiguration files with secrets, keys and tokens are read from the server.
  3. T1213 Data from Information RepositoriesSource code and other repository content is read.
  4. T1195.002 Compromise Software Supply ChainStolen CI/CD tokens can be used to change code or builds that reach customers.

What to do

  1. Upgrade self-managed GitLab to 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 or later, as described in GitLab's patch release notes.
  2. Review web and API logs for unauthenticated requests to the commits API.
  3. Rotate secrets that live on the server, such as runner registration tokens, CI/CD variables, deploy keys and integration credentials.
  4. If you find signs of compromise, review recent commits, pipeline changes and releases for changes you did not make.
Written with AI from the sources on this page on 23 Oct 2026. Check the vendor's advisory before you act.

[ Description ]Official 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.

CISA: 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.

[ Fixes ]Fixes and patches

CISA required action (US federal deadline 14 Sep 2026): 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.

  • Security bulletin: GitLabVendor patch or bulletin · CERT-FR · docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-9-released, cited by CERT-FR CERTFR-2026-AVI-1242

[ Advisories ]Government CERT advisories

  • CERT-FRCERTFR-2026-AVI-1242

    Multiple vulnerabilities in GitLab Translated from French

    Multiple vulnerabilities have been discovered in GitLab. They allow an attacker to cause a breach of data confidentiality and a security policy bypass. Gitlab reports that vulnerability CVE-2026-85706 is being actively…

    CVE-2026-85706CVE-2026-87719

[ References ]References