← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-85706 exploited? Yes: in CISA KEV since 11 Sep 2026

Gociux · GitLab Community Edition and Enterprise Edition · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-85706, GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 11 Sep 2026. It affects GitLab Community Edition and Enterprise Edition. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 11 Sep 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity10CVSS 3.1 · critical
US federal due14 Sep 2026BOD 22-01 deadline

What it is

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.

VendorGitLab (6 exploited CVEs in KEV)
ProductCommunity Edition and Enterprise Edition
VulnerabilityGitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
WeaknessCWE-35
Published12 Sep 2026
Added to KEV11 Sep 2026
Reported by (CNA)GitLab

What to do

  1. Check whether you run it. Look for Community Edition and Enterprise Edition in your asset inventory, including appliances and cloud images. Stack check lists every exploited GitLab CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 12 Sep 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for GitLab.

Other exploited CVEs in Community Edition and Enterprise Edition

References

Questions

Is CVE-2026-85706 being exploited?

Yes. CISA added CVE-2026-85706 to the Known Exploited Vulnerabilities catalog on 11 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-85706 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-85706?

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. Check GitLab's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Community Edition and Enterprise Edition and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · GitLab scorecard · act-now radar.

Running GitLab in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →