CVE
GitLab cache poisoning in Maven virtual registry
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 19.3.9, 19.4.8, 19.5.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 37/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
GitLab EE, in the GitLab product, can let someone who controls an upstream repository alter cached Maven packages belonging to other repositories in the same virtual registry, because responses are not properly validated. An attacker can do this remotely and without logging in, and the flaw is triggered only under certain conditions.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an individual controlling an upstream repository to alter cached Maven packages from other repositories in the same virtual registry due to improper response validation.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach14/20Affects GitLab (an enterprise product or network appliance)
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-112203 (Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-112203 (entry last updated 2026-11-17):
Affected:
- GitLab GitLab: from 18.2, fixed in 19.3.9; from 19.4, fixed in 19.4.8; from 19.5, fixed in 19.5.6
Fixed versions: 19.3.9, 19.4.8, 19.5.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-112203 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112203 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.com/gitlab-org/gitlab/-/work_items/633373
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-112203
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-112203"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- GitLab GitLab
From 18.2 · fixed in 19.3.9; From 19.4 · fixed in 19.4.8; From 19.5 · fixed in 19.5.6
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112203
Is CVE-2026-112203 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-112203?
GitLab: from 18.2 before 19.3.9; from 19.4 before 19.4.8; from 19.5 before 19.5.6.Source: cve.now feed data
How do I fix CVE-2026-112203?
Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.Source: cve.now feed data