CISA Warns of Critical GitLab RCE Vulnerability Actively Exploited in Attacks

The Cybersecurity and Infrastructure Security Agency has flagged a critical vulnerability in GitLab Community Edition and Enterprise Edition as actively exploited, placing organizations running vulnerable servers under urgent pressure to remediate.

Tracked as CVE-2026-97229, the flaw allows unauthenticated attackers to execute arbitrary code through a specially crafted regular expression embedded in a CI/CD configuration.

According to the supplied CISA advisory, the vulnerability was added to the agency’s Known Exploited Vulnerabilities catalog on October 29, 2026, with a remediation deadline of November 1, 2026.

CISA Warns of Critical GitLab RCE Vulnerability

The entry also requires forensic triage under Binding Operational Directive 26-04, making investigation an explicit component of the response.

GitLab’s published CVE record assigns the vulnerability a maximum CVSS v3.1 score of 10.0. Its vector identifies a network-accessible attack requiring low complexity, no privileges, and no user interaction.

The underlying weakness is classified as CWE-190, Integer Overflow or Wraparound. GitLab attributes the vulnerability to insufficient regular expression validation when processing CI/CD configuration content.

Under certain conditions, an attacker-controlled expression can lead to arbitrary code execution on the GitLab server, rather than merely disrupting pipeline execution.

Integer overflow occurs when a calculation produces a value outside the range its numeric representation can hold. Depending on the implementation, the result may wrap to a smaller or negative value, undermining assumptions used in allocation, validation, or execution logic.

Affected releases include GitLab versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. GitLab identifies versions 19.2.8, 19.3.5, and 19.4.2 as remediating the issue in their respective release branches.

The CVE record was published on October 13, 2026, and credits researcher joaxcar with reporting the vulnerability through GitLab’s HackerOne program.

The supplied CISA entry directs stakeholders to apply vendor-prescribed mitigations while following BOD 26-04, titled “Prioritizing Security Updates Based on Risk,” and the agency’s forensic triage requirements.

Organizations must evaluate each asset’s internet exposure when determining the applicable patching requirements. The directive also calls for following applicable guidance for cloud services or discontinuing use of the affected product when mitigations are unavailable.

The November 1 deadline leaves a short response window between catalog inclusion and required remediation, reinforcing the urgency of identifying affected deployments.

CISA lists the vulnerability’s use in ransomware campaigns as unknown. That designation should not be interpreted as evidence that ransomware activity has occurred or been ruled out.

The supplied entry names no threat actors, victims, malware families, or exploitation indicators, leaving the campaign’s operational scope undisclosed.

Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team 

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories