Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege GitLab user
-
DeliveryCraft malicious repository reference
-
ExploitPoison cached raw file response
-
ExecutionVictim CI/CD pipeline executes crafted content
-
ImpactExfiltrate protected environment variables
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Permissive regular expression
|
| Exploitation Conditions | Requires an authenticated low-privileged GitLab account (PR:L) with network access to the instance, and the ability to poison the cache for raw repository file responses by supplying crafted repository references (CWE-625, improper reference validation). Exploitation is gated by 'certain conditions' and rated AC:H - the attacker must win specific cache/timing state AND a targeted victim's CI/CD pipeline must fetch and execute the poisoned raw file for impact (secret exposure) to occur. Limiting factors: authentication is mandatory, high attack complexity, and success depends on a victim pipeline actually running the poisoned content rather than default unauthenticated remote code execution. |
| Impact | This is a credible, high-priority issue but not an emergency. The CVSS 8.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N) reflects a network-reachable, authenticated (PR:L) flaw with high attack complexity (AC:H) and a scope change (S:C) because a low-privileged attacker can affect OTHER users' CI/CD pipelines and expose their protected environment variables (C:H/I:H). Public exploit code exists (referenced HackerOne report #3832707), which raises practical risk above a theoretical finding. However, there is NO EPSS score and NO SSVC decision data provided, and the CVE is NOT on CISA KEV - so there is no evidence of active exploitation; POC availability and active exploitation are distinct signals and must not be conflated. The AC:H metric and the description's 'under certain conditions' language indicate exploitation is non-trivial and likely requires specific timing/cache state plus a target whose pipeline runs the poisoned content, which tempers the real-world probability despite the high base score. Net: treat as a priority patch for GitLab operators (public POC + protected-secret exposure), but absent KEV/EPSS this is most plausibly opportunistic or targeted rather than mass-exploited. |
| Exploit ScenarioDerived | A low-privileged authenticated GitLab user abuses improper validation of repository references to poison the cached response for a raw repository file. When a targeted victim's CI/CD pipeline subsequently fetches that cached raw file, it executes attacker-crafted content and may leak the victim's protected CI/CD environment variables. A public proof-of-concept is documented in HackerOne report #3832707, lowering the barrier to replication, though the CVSS AC:H rating indicates the specific cache/timing conditions are not trivial to meet. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Cache poisoning of raw repository file responses in GitLab CE/EE (all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2) lets a low-privileged authenticated user supply crafted repository references so that cached raw-file content is served to other users. When a targeted victim's CI/CD pipeline subsequently fetches that poisoned raw file, the pipeline executes attacker-controlled content, potentially exposing protected environment variables. Publicly available exploit code exists (referenced via a HackerOne report), but the issue is not confirmed as actively exploited (no CISA KEV listing); exploitation is rated high complexity (AC:H), requires authentication (PR:L), and success depends on a victim pipeline actually pulling and running the poisoned content, making this a credible, high-priority issue rather than an emergency.
RemediationAI
Vendor-released patch: upgrade to GitLab 19.2.8, 19.3.5, or 19.4.2 (or later) as described in the patch release advisory at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/. Prioritize internet-exposed or multi-tenant instances and any instance where untrusted users can create projects, since the prerequisite is only a low-privileged authenticated account. If immediate upgrade is not possible, reduce exposure by disabling or shortening cache lifetimes for raw repository file responses at the reverse proxy/CDN in front of GitLab (note this increases load on GitLab and may not fully eliminate the race), restricting project creation and CI/CD runner usage to trusted users, and moving sensitive values out of protected CI/CD variables into an external secrets manager or masking+protected-branch configuration that limits which pipelines can read them (this changes pipeline configuration and may break jobs that rely on those variables). Additionally, audit CI/CD job logs and pipeline activity for unexpected raw-file fetches, and rotate any protected environment variables that may have been exposed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GitLab CE/EE serves raw repository files (for example, files fetched by CI/CD jobs and by include: directives) through a caching layer, and validates the repository reference used to build that cache key. CWE-625 (Permissive Regular Expression) is the mapped root-cause class: the validation pattern used for repository references was insufficiently strict, so crafted references could collide with or hijack the cache entry for a legitimate raw-file response. Because the cache is shared across users on the same instance, an attacker with a low-privileged account (CVSS vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N) can poison the stored response and have it delivered to a different user. The scope change (S:C) reflects that the impact crosses from the attacker's repository context into the victim's CI/CD pipeline execution context, where the injected content runs and can reach protected environment variables. The attack is network-reachable but gated by high complexity: the attacker must win specific cache/timing state, and a victim pipeline must actually fetch and execute the poisoned raw content before any confidentiality or integrity impact is realized.
Know when Gitlab gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Network-reachable but needs a low-priv account (PR:L) and specific cache/timing conditions (AC:H); poisoning other users' pipelines crosses a trust boundary (S:C) exposing secrets and executing content (C:H/I:H), with no availability impact (A:N).
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
2DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed a user to poison cached responses for raw repository files, causing targeted users' CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references.
Executive ViewAI
GitLab CE/EE deployments are exposed to a cache-poisoning issue affecting raw repository file responses, allowing a low-privileged authenticated user to serve crafted content that a victim's CI/CD pipeline may later execute and thereby expose protected environment variables. Leadership should treat this as a high business risk to software supply chain integrity and development secrets, even though exploitation requires authentication, high complexity, and a victim pipeline actually pulling the poisoned file. Publicly available exploit code exists, but no CISA KEV listing was provided, and no vendor-released patch has been identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or bypassing caching for raw repository file responses at the reverse proxy/CDN layer, purging existing caches, restricting authenticated users who can create crafted repository references, enforcing protected and scoped CI/CD variables, monitoring raw-file fetches and pipeline execution for anomalies, and rotating exposed CI/CD secrets if suspicious activity is detected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in GitLab CE/EE Authorization and Access Control Flaws
View all 24An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Authenticated code execution on the GitLab server is possible in GitLab CE/EE 19.2 through 19.4.0, where an integer over
Authenticated users who can define or modify a CI/CD configuration can achieve remote code execution on GitLab CE/EE ser
Unauthenticated path traversal in the @zereight/mcp-gitlab Model Context Protocol server prior to version 2.1.27 allows
EUVD-2026-98224
GHSA-49c6-8ph4-9vr9
NVD
CVE.org
EPSS
Exploit-DB