Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public GitLab project over network
-
ExploitCraft malicious GraphQL API query
-
ExecutionBypass authorization on notes
-
ImpactRead internal and confidential system notes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a GitLab CE/EE instance running an affected version (19.2-19.2.7, 19.3-19.3.4, or 19.4-19.4.1) that hosts public projects containing internal notes or confidential system notes; the attacker queries these through the GraphQL API, which fails to properly enforce authorization under certain conditions. No authentication is required (PR:N), but the exposure is inherently limited: only public projects are affected, only note content is readable (no write or service impact), and instances already patched to 19.2.8 / 19.3.5 / 19.4.2 or later are not vulnerable. Internet-exposed, unpatched instances with active public projects face the highest realistic risk. |
| Impact | This is a moderate-severity information-disclosure flaw (CVSS 5.3) rooted in improper authorization (CWE-863) in GitLab's GraphQL API. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) is internally consistent and signals a network-reachable, low-complexity, unauthenticated issue with only a limited confidentiality impact and no integrity or availability impact - explaining the mid-range 5.3 rather than a critical rating. Publicly available exploit code exists (referenced HackerOne report #3975416), which raises the practical likelihood of opportunistic testing, but this is NOT confirmed active exploitation: the CVE is not listed in CISA KEV and no EPSS score was provided in the input, so widespread in-the-wild abuse cannot be asserted. The bug was reported by GitLab itself and patched across the affected branches, consistent with responsible disclosure rather than observed attacks. Net assessment: a real but bounded priority - the unauthenticated network vector plus a public POC warrant prompt patching for internet-exposed GitLab instances, yet the impact is confined to reading internal and confidential system notes on public projects, with no data modification or service disruption, so it is not a drop-everything critical. No signals directly conflict; the main gap is the absence of EPSS/KEV data to gauge real-world exploitation velocity. |
| Exploit ScenarioDerived | An unauthenticated attacker sends crafted GraphQL queries over the network to a vulnerable GitLab instance hosting public projects, retrieving internal notes and confidential system notes that should be restricted to authorized members. Because publicly available exploit code exists (HackerOne report), the technique can be reproduced with low effort and no authentication, though the leaked data is limited to note contents rather than full repository or credential access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Unauthenticated attackers can read internal notes and confidential system notes on public GitLab CE/EE projects through the GraphQL API, which fails to enforce proper authorization checks on affected versions (19.2 through 19.2.7, 19.3 through 19.3.4, and 19.4 through 19.4.1). The flaw carries a CVSS 3.1 score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), reflecting a confidentiality-only impact with no integrity or availability effect. Publicly available exploit code exists, with a HackerOne report and a GitLab work item referenced, so unpatched, internet-exposed instances hosting public projects with internal or confidential notes are the highest-priority targets for remediation.
RemediationAI
Upgrade GitLab CE/EE to 19.2.8, 19.3.5, or 19.4.2 (whichever corresponds to your release line) as the primary fix; the vendor patch release notes are at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/ and the tracking issue is at https://gitlab.com/gitlab-org/gitlab/-/work_items/627709. If immediate patching is not possible, reduce exposure by changing public projects that contain internal or confidential notes to internal or private visibility - the trade-off is that this breaks anonymous browsing, cloning over HTTPS without credentials, and any public CI or badge links. As a narrower interim control, restrict network access to the GraphQL endpoint (/api/graphql) at the reverse proxy or WAF for unauthenticated clients while leaving the REST API and web UI functional; this may break legitimate anonymous GraphQL consumers and integrations, so validate before enabling. Disabling the internal-notes feature globally is not a supported toggle and would degrade collaboration, so it is not recommended. After patching, audit logs for anonymous GraphQL queries against note-related fields in public projects during the exposure window, since any note content readable before the fix should be treated as potentially disclosed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is an improper authorization defect (CWE-863) in GitLab's GraphQL API. GitLab models comments and system-generated activity as "notes," and some notes are flagged internal (visible only to project members) or confidential (restricted system notes). On public projects, the GraphQL API resolvers - the code path that maps note objects and their fields to a query response - apparently omitted or misapplied the visibility check that the REST API and web UI enforce, allowing a requester with no session to retrieve the content of internal and confidential notes. Because GraphQL exposes data through a typed schema rather than fixed endpoints, a single missing field-level authorization guard can leak objects that would otherwise be filtered, which matches the "under certain conditions" qualifier in the vendor description. The CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* confirms the affected component is the core GitLab application itself (both Community and Enterprise editions), not a separate plugin or dependency. The access vector is network-based with no privileges or user interaction required (PR:N/UI:N), but scope is unchanged and the impact is limited to low confidentiality loss: attackers read note content, they cannot alter records or disrupt service.
Know when Gitlab gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated GraphQL API access over the network gives AV:N/AC:L/PR:N/UI:N; impact is limited disclosure of notes, so C:L with I:N/A:N and no scope change.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
2DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to read internal notes and confidential system notes on public projects due to improper authorization in the GraphQL API.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in GitLab CE/EE Authorization and Access Control Flaws
View all 24An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Authenticated code execution on the GitLab server is possible in GitLab CE/EE 19.2 through 19.4.0, where an integer over
Authenticated users who can define or modify a CI/CD configuration can achieve remote code execution on GitLab CE/EE ser
Unauthenticated path traversal in the @zereight/mcp-gitlab Model Context Protocol server prior to version 2.1.27 allows
EUVD-2026-98217
GHSA-v4cm-2jq7-xgmq
NVD
CVE.org
EPSS
Exploit-DB