Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab
GitLab CE/EE versions 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 are affected. Fixed in 19.3.6, 19.4.3, and 19.5.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 19.3.6, 19.4.3, 19.5.1
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have poisoned a shared cache's OAuth/OIDC discovery document to redirect certain flows to an externally controlled server, due to improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- GitLab GitLab
From 18.3 · fixed in 19.3.6; From 19.4 · fixed in 19.4.3; From 19.5 · fixed in 19.5.1
- gitlabBitnami
From 18.3.0 · fixed in 19.3.6; From 19.4.0 · fixed in 19.4.3; From 19.5.0 · fixed in 19.5.1
References 2
gitlab.com
docs.gitlab.com
Questions about CVE-2026-112212
What does this mean?
An unauthenticated user could poison a shared cache's OAuth/OIDC discovery document, redirecting certain flows to an externally controlled server.Source: docs.gitlab.com
Am I affected, and how do I check?
The advisory lists GitLab CE/EE 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1. It says poisoning requires 'certain conditions' but does not detail them, so check the installed GitLab version against those ranges.Source: docs.gitlab.com
What should I do about it?
Upgrade to 19.3.6, 19.4.3, or 19.5.1, matching your release line.Source: docs.gitlab.com
Is it 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