Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab

published 2026-10-13 27 d ago modified 2026-10-16 23 d ago also BIT-gitlab-2026-100755 , EUVD-2026-98211

cvss: 4.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

bitnami gitlab 19.2.8, 19.3.5, 19.4.2
GitLab GitLab 19.2.8, 19.3.5, 19.4.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 25 d ago (2026-10-14)

Exploit prediction

0.09% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.6	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
OSV	3.1	4.6	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=16.2.0, <19.2.8 >=19.3.0, <19.3.5 >=19.4.0, <19.4.2	19.2.8 19.3.5 19.4.2

Affected products

GitLab GitLab

Classification

Weakness

CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data

Technology feeds

GitLab rss critical rss

References

docs.gitlab.com /releases/patches/patch-release-gitlab-19-4-2-released/
release-notes, vendor-advisory, advisory
gitlab.com /gitlab-org/gitlab/-/work_items/627507
issue-tracking, report
nvd.nist.gov /vuln/detail/CVE-2026-100755
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary