CVE-2026-8472 Vulnerability Analysis & Exploit Details

CVE-2026-8472
Vulnerability Scoring

4.3
/10
Medium Risk

The vulnerability CVE-2026-8472 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-8472 Details

Status: Analyzed

Last updated: 🕐 10 Jul 2026, 13:02 UTC
Originally published on: 🕘 08 Jul 2026, 21:16 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

cve@gitlab.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVE-2026-8472 Vulnerability Summary

CVE-2026-8472: GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with minimal access permissions to read work item metadata from private projects due to missing authorization checks.

Assessing the Risk of CVE-2026-8472

Access Complexity Graph

The exploitability of CVE-2026-8472 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-8472

CVE-2026-8472 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-8472, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-8472, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-8472 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-8472 poses no threat to data integrity.
  • Availability: None
    CVE-2026-8472 does not impact system availability.

CVE-2026-8472 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:gitlab:gitlab:18.9.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.8:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.8:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.9.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.9.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.8:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.8:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.10.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.10.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.11.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.11.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.0.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.0.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.1:*:*:*:community:*:*:*

Protect Your Infrastructure against CVE-2026-8472: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-90474 – MCPHub before 1.0.32 contains an authentication bypass vulnerability in its embedded OAuth 2.0 authorization server where client authentication is ...
  • CVE-2026-90473 – msgpack-java through 0.9.12 contains an integer overflow vulnerability in MessageUnpacker.skipValue() when processing MAP32 containers with large e...
  • CVE-2026-90472 – msgpack-java through 0.9.12 contains a stack overflow vulnerability in MessageUnpacker.unpackValue() that recursively deserializes arrays and maps ...
  • CVE-2026-89172 – Improper protection of physical side channels vulnerability in Microchip AN1044, Microchip AN953, and Microchip SW300052. This issue affects AN104...
  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...