CVE-2026-0958 Vulnerability Analysis & Exploit Details

CVE-2026-0958
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-0958 poses a critical security risk that could lead to severe breaches.

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: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-0958 Details

Status: Analyzed

Last updated: 🕞 13 Feb 2026, 15:33 UTC
Originally published on: 🕛 11 Feb 2026, 12:16 UTC

Time between publication and last update: 2 days

CVSS Release: version 3

CVSS3 Source

cve@gitlab.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-0958 Vulnerability Summary

CVE-2026-0958: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to cause denial of service through memory or CPU exhaustion by bypassing JSON validation middleware limits.

Assessing the Risk of CVE-2026-0958

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2026-0958 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-0958, 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-0958, 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-0958 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-0958 poses no threat to data integrity.
  • Availability: High
    CVE-2026-0958 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-0958 References

External References

CWE Common Weakness Enumeration

CWE-436

CAPEC Common Attack Pattern Enumeration and Classification

  • HTTP Request Splitting CAPEC-105 An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to split a single HTTP request into multiple unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server). See CanPrecede relationships for possible consequences.
  • HTTP Response Smuggling CAPEC-273 An adversary manipulates and injects malicious content in the form of secret unauthorized HTTP responses, into a single HTTP response from a vulnerable or compromised back-end HTTP agent (e.g., server). See CanPrecede relationships for possible consequences. Modification/manipulation of HTTP message headers, request-line and body parameters to disrupt and interfere in the interpretation and parsing of HTTP message lengths/boundaries for consecutive HTTP messages by HTTP agents in a HTTP chain or network path.
  • HTTP Response Splitting CAPEC-34 An adversary manipulates and injects malicious content, in the form of secret unauthorized HTTP responses, into a single HTTP response from a vulnerable or compromised back-end HTTP agent (e.g., web server) or into an already spoofed HTTP response from an adversary controlled domain/site. See CanPrecede relationships for possible consequences.

Vulnerable Configurations

  • cpe:2.3:a:gitlab:gitlab:18.4.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.4.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.4.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.5.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.5.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.6.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.6.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.7.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.7.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:18.8.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:18.8.3:*:*:*:enterprise:*:*:*

Protect Your Infrastructure against CVE-2026-0958: 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-2565 – A weakness has been identified in Wavlink WL-NU516U1 20251208. Affected by this issue is the function sub_40785C of the file /cgi-bin/adm.cgi. This...
  • CVE-2026-2564 – A security flaw has been discovered in Intelbras VIP 3260 Z IA 2.840.00IB005.0.T. Affected by this vulnerability is an unknown functionality of the...
  • CVE-2026-2101 – A Reflected Cross-site Scripting (XSS) vulnerability affecting ENOVIAvpm Web Access from ENOVIAvpm Version 1 Release 16 through ENOVIAvpm Version 1...
  • CVE-2026-26930 – SmarterTools SmarterMail before 9526 allows XSS via MAPI requests.
  • CVE-2026-2563 – A vulnerability was identified in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. Affected is the function set_stcreenen_deabled_status/get_status ...