CVE-2026-75975 Vulnerability Analysis & Exploit Details

CVE-2026-75975
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-75975 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-75975 Details

Status: Analyzed

Last updated: 🕝 02 Sep 2026, 14:44 UTC
Originally published on: 🕙 24 Aug 2026, 10:16 UTC

Time between publication and last update: 9 days

CVSS Release: version 3

CVSS3 Source

ce714d77-add3-4f53-aff5-83d477b104bb

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-75975 Vulnerability Summary

CVE-2026-75975: fast-uri is a URI parser for Node.js. Its custom parser for bracketed IPv6 literals does not validate the complete IPv6 grammar, so invalid trailing text in an authority can be silently discarded and a malformed attacker-controlled host is turned into a different valid IPv6 destination. For example, a bracketed literal with invalid trailing characters is normalized to the unspecified address, which a Node HTTP client then connects to a local service over loopback, and other malformed literals collapse to private-range addresses. No error is set on the parsed result, so an application checking the error field cannot detect the rewrite. An application that normalizes untrusted URLs before outbound requests, redirects, proxy routing, or address-policy enforcement can be redirected to a local or private IPv6 target, giving a server-side request forgery and address-policy bypass primitive. The affected versions are 2.3.1 up to but not including 2.4.5, 3.0.0 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which validate bracketed IP literals against the full grammar and mark malformed literals as authority errors. Users should upgrade to a patched version.

Assessing the Risk of CVE-2026-75975

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2026-75975 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-75975, 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-75975, 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-75975 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2026-75975 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-75975 does not impact system availability.

CVE-2026-75975 References

External References

CWE Common Weakness Enumeration

CWE-918

CAPEC Common Attack Pattern Enumeration and Classification

  • Server Side Request Forgery CAPEC-664 An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

Vulnerable Configurations

  • cpe:2.3:a:openjsf:fast-uri:2.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:2.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:2.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:2.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:2.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:2.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:2.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:3.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:3.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:4.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:4.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:4.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:4.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openjsf:fast-uri:4.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openjsf:fast-uri:4.1.2:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-75975: 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-97318 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not properly validate a giveaway's parent page URL before saving it...
  • CVE-2026-97317 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not remove the reCAPTCHA secret key from the giveaway settings it e...
  • CVE-2026-94298 – The BuildKit WordPress plugin before 1.0.29 does not properly sanitise and escape data submitted by contributor-level users before storing it and ...
  • CVE-2026-92820 – The Ninja Forms - File Uploads plugin for WordPress is vulnerable to arbitrary file operations in all versions up to, and including, 3.3.34 via the...
  • CVE-2026-92174 – The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.73.2 via the 'them...