Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab
Impact
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.
Source excerpt · GitLabGitLab 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.
What to do
Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
GitLab · GitLab
GitLab
3 ranges
GitLab · GitLab
GitLab
Compare with this publisher’s ranges. This does not inspect your installation.
affected
18.3 → before 19.3.6
semver versions
19.4 → before 19.4.3
semver versions
19.5 → before 19.5.1
semver versions
Other versions: unaffected
Product identifiers (CPE)
cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-112212View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.