How severe is CVE-2026-85706?

CVE-2026-85706 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-85706 being actively exploited?

Yes. CVE-2026-85706 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-09-11, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2026-85706?

CVE-2026-85706 primarily affects Gitlab. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-85706?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

When was CVE-2026-85706 published?

CVE-2026-85706 was published on 2026-09-12 and last updated on 2026-09-14.

CVE-2026-85706

CVE-2026-85706 is a critical-severity vulnerability in Gitlab with a CVSS 3.x base score of 10.0. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-09-11). The underlying weakness is classified as CWE-22.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
EPSS exploit prediction: 15% (96th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2026-09-11)
Weakness: CWE-22
Affected product: Gitlab
Published: 2026-09-12
Last modified: 2026-09-14

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.

Frequently asked questions

What is CVE-2026-85706?: 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.
How severe is CVE-2026-85706?: CVE-2026-85706 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-85706 being actively exploited?: Yes. CVE-2026-85706 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-09-11, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2026-85706?: CVE-2026-85706 primarily affects Gitlab. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-85706?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
When was CVE-2026-85706 published?: CVE-2026-85706 was published on 2026-09-12 and last updated on 2026-09-14.

References

Affected products (2)

cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Gitlab

CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
CVE-2023-7028 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9,…
CVE-2023-2825 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting only version 16.0.0. An unauthenticated malicious user can use a…
CVE-2022-0735 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions…
CVE-2021-22205 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. GitLab was not properly…
CVE-2019-9174 — Critical (CVSS 10.0): An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x…

All CVEs affecting Gitlab →

Other CWE-22 (Path Traversal) vulnerabilities

CVE-2026-70200 — Critical (CVSS 10.0): Improper limitation of a pathname to a restricted directory ('path traversal') in Azure Logic Apps allows an…
CVE-2026-76606 — Critical (CVSS 10.0): Joomla Extension - fabrikar.com - Path Traversal via image element in Fabrik < 4.7.2.
CVE-2026-18051 — Critical (CVSS 10.0): The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path it uses to build cache…
CVE-2026-74764 — Critical (CVSS 10.0): Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a…
CVE-2026-16940 — Critical (CVSS 10.0): The Custom Fields WordPress plugin before 1.5.1 does not validate a user-supplied file path before deletion, allowing…
CVE-2026-67429 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, image.download and related…

Browse all CWE-22 (Path Traversal) vulnerabilities →