Skip to content
StrikeCyberStrikeCyber
Threat Radar · Actively exploited

GitLab Community Edition and Enterprise Edition (CVE-2026-97229)

Exploited in the wild Added October 29, 2026 EPSS 69.3%Dev tools

Quick answer

Yes. CVE-2026-97229 in GitLab Community Edition and Enterprise Edition is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on October 29, 2026. If you run Community Edition and Enterprise Edition, apply the vendor's fix now and check for signs of compromise.

ConfirmedExploited in the wild
Not knownRansomware use
69.3%EPSS · top 1%
October 29,Added to CISA KEV

What is CVE-2026-97229?

GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability. GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.

Description from the CISA Known Exploited Vulnerabilities catalogue.

What kind of flaw is it?

Integer overflowCWE-190

A number wraps around its limit, leading to undersized buffers and memory corruption.

Other exploited integer overflow

Why it matters

Source code platforms, build servers and collaboration tools hold code, secrets and credentials. Exploiting them can lead to supply chain attacks on everyone who uses your software.

Likelihood of exploitation activity in the next 30 days (EPSS)69.3%

Higher than 99% of all scored vulnerabilities.

Am I affected? How to check

  1. 1Confirm whether you self-host the affected tool.
  2. 2Check versions against the advisory and whether the instance is internet-facing.
  3. 3Review audit logs for new tokens, accounts or changes to pipelines.

What to do now

  1. 1Apply the vendor fix.
  2. 2Rotate tokens and secrets stored in the platform if exposure is possible.
  3. 3Restrict access to internal networks or SSO-protected access.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

Deadline and priority

CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (November 1, 2026 for this one), and strongly urges every organization to prioritize them the same way.

In the news

More in the daily briefing.

Common questions

Is CVE-2026-97229 being exploited?

Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on October 29, 2026.

How do I fix CVE-2026-97229?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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 the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.

Is my GitLab Community Edition and Enterprise Edition affected?

Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.

Sources

(877) 657-8496