CVE-2026-15387 Vulnerability Analysis & Exploit Details

CVE-2026-15387
Vulnerability Scoring

4.3
/10
Medium Risk

The vulnerability CVE-2026-15387 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-15387 Details

Status: Analyzed

Last updated: 🕞 31 Aug 2026, 15:41 UTC
Originally published on: 🕑 26 Aug 2026, 14:17 UTC

Time between publication and last update: 5 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:N/I:L/A:N

CVE-2026-15387 Vulnerability Summary

CVE-2026-15387: GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have influenced the execution environment of Pipeline Execution Policy enforcement jobs, due to improper handling of job dependencies.

Assessing the Risk of CVE-2026-15387

Access Complexity Graph

The exploitability of CVE-2026-15387 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-15387

CVE-2026-15387 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-15387, 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-15387, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-15387 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2026-15387 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-15387 does not impact system availability.

CVE-2026-15387 References

External References

CWE Common Weakness Enumeration

CWE-349

CAPEC Common Attack Pattern Enumeration and Classification

  • Cache Poisoning CAPEC-141 An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.
  • DNS Cache Poisoning CAPEC-142 A domain name server translates a domain name (such as www.example.com) into an IP address that Internet hosts use to contact Internet resources. An adversary modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the adversary specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Adversaries can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.

Vulnerable Configurations

  • 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:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.1.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.1.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.2.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.2.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:19.3.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:19.3.0:*:*:*:enterprise:*:*:*

Protect Your Infrastructure against CVE-2026-15387: 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-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...