CVE-2026-18252VulnerabilityPublished 1 Sep 2026Updated 10 Sep 2026

CVE-2026-18252: Inclusion of Functionality from Untrusted Control Sphere in GitLab

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 19.3.1 : patch gitlab soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.3.1, 19.2.5, 19.1.7

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 19.3.1, 19.2.5 or 19.1.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=18.9.0 <19.1.7 >=19.2.0 <19.2.5 >=19.3.0 <19.3.1	Fixed in 19.1.7 19.2.5 19.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released by GitLab. Users should upgrade to versions 19.1.7, 19.2.5, or 19.3.1 or later to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the official fixes.

Description

A vulnerability in GitLab EE versions 18.9 up to but not including 19.1.7, 19.2 up to but not including 19.2.5, and 19.3 up to but not including 19.3.1 allowed an authenticated user with developer-role permissions to execute arbitrary commands in a CI context. This occurred due to the Claude agent processing configuration from a user-controlled source. The issue has been remediated in the specified fixed versions.

References

Community reviews

Loading reviews…