CVE-2026-100755
4.6MediumPublished 13 Oct 2026 · NVD status: Analyzed · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- Required
- Impact
- Limited impact
- Weakness
- CWE-349
Impact
Authenticated attackers can poison cached page content to serve tampered data to other users. This requires network access and an authenticated GitLab account under specific deployment configurations.
Root cause
Improper cache key construction allows cached page responses to collide across different user requests.
Affected systems
GitLab CE/EE versions 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Fix & remediation
Upgrade GitLab CE/EE to version 19.2.8, 19.3.5, 19.4.2, or later. No interim mitigations are documented in the advisory.
$ gitlab-rake gitlab:env:infoAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain deployment configurations, could have allowed an authenticated user to poison cached page content served to other users due to improper cache key construction.
References
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/Release NotesVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/work_items/627507Issue Tracking