Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-100755— Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab

Quick assessment

Affected
GitLab GitLab
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

GitLab 已修复 GitLab CE/EE 中存在的一项漏洞，该漏洞影响所有在 16.2 至 19.2.8 之前、19.3 至 19.3.5 之前以及 19.4 至 19.4.2 之前的版本。在某些部署配置下，由于缓存键构造不当，攻击者可能通过缓存投毒（cache poisoning）手段，使其他用户受到影响，从而将恶意或错误的内容注入到缓存的页面内容中。

CVSS 4.6 · Medium EPSS 0.08% · P0

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 3

VendorProduct Version RangeStatus
GitLab GitLab 16.2< 19.2.8 affected
19.3< 19.3.5 affected
19.4< 19.4.2 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-100755

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
在可信数据中接受外来的不可信数据
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
GitLab GitLab 16.2 ~ 19.2.8 cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*

II. Public POCs for CVE-2026-100755

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-100755

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-100755 (1)

Same Patch Batch · GitLab · 2026-10-13 · 24 CVEs total

CVE-2026-97229 10.0 CRITICAL Integer Overflow or Wraparound in GitLab
CVE-2026-92883 8.7 HIGH Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Gi
CVE-2026-16301 8.5 HIGH Incorrect Authorization in GitLab
CVE-2026-14814 8.2 HIGH Permissive Regular Expression in GitLab
CVE-2026-81839 7.7 HIGH Incorrect Authorization in GitLab
CVE-2026-96893 7.3 HIGH Improper Neutralization of Input Used for LLM Prompting in GitLab
CVE-2026-101168 6.2 MEDIUM Insertion of Sensitive Information into Log File in GitLab
CVE-2026-7767 5.8 MEDIUM URL Redirection to Untrusted Site ('Open Redirect') in GitLab
CVE-2026-84284 5.3 MEDIUM Incorrect Authorization in GitLab
CVE-2026-85529 5.3 MEDIUM Incorrect Authorization in GitLab
CVE-2026-16275 5.3 MEDIUM Incorrect Authorization in GitLab
CVE-2026-14552 4.3 MEDIUM Incorrect Authorization in GitLab
CVE-2026-14210 4.3 MEDIUM Insufficient Granularity of Access Control in GitLab
CVE-2026-6567 4.3 MEDIUM Incorrect Authorization in GitLab
CVE-2026-105458 4.3 MEDIUM Reliance on Untrusted Inputs in a Security Decision in GitLab
CVE-2026-104661 4.3 MEDIUM Incorrect Privilege Assignment in GitLab
CVE-2026-92528 4.2 MEDIUM Incorrect Authorization in GitLab
CVE-2026-78335 4.2 MEDIUM Incorrect Authorization in GitLab
CVE-2026-5954 4.2 MEDIUM Incorrect Authorization in GitLab
CVE-2026-100104 3.5 LOW Server-Side Request Forgery (SSRF) in GitLab

Showing top 20 of 24 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: GitLab
Same vendor: GitLab
Same weakness: CWE-349

V. Comments for CVE-2026-100755

No comments yet

Leave a comment