FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2026-97229

GitLab · Community Edition and Enterprise Edition · GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 1% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-10-29 · exploited in the wild for 9 days

How a test catches it

Test
Submit boundary values to every parameter that reaches an arithmetic or allocation decision: the maximum, one past it, negative, zero, and a non-numeric string where a number is expected.
Passes when
Each is rejected or clamped, and the resulting index or allocation is computed in a width that cannot wrap. A value that parses as a number and then behaves as a different one is the finding, and it is invisible without testing the boundaries.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 10.0 CRITICAL. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionnonecan be triggered with nobody interacting with the page or request
Base vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
WeaknessCWE-190

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.6522, which places it in the top 1% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.6522
Percentile0.993 — top 1%

Time

Added to KEV2026-10-29
Days exploited9
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

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.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed 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.

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service