Public vulnerability disclosure

CVE-2026-111753

Angular: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)

publishedCWE-201CWE-359

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser. With XSRF protection enabled, a mutating HTTP request to an attacker-controlled URL containing backslashes, stripped control characters or spaces, or removable ASCII whitespace can be misclassified as relative and same-origin, causing the interceptor to attach the X-XSRF-TOKEN header before the browser dispatches the request to a cross-origin host. With permissive CORS handling for the custom header, the attacker can obtain the victim's XSRF token and use it to perform cross-site request forgery against the victim session. This issue is fixed in versions 20.3.34 and 21.0.3.

Technical severity5.9 mediumCVSS 4.0 · CNA: GitHub_M
Published2026-11-05Source updated 2026-11-09
Collected2026-11-105 attributed sources

Fixes and workarounds

Fix

@angular/common (npm): GitHub reports patched versions 21.0.3. Check the advisory for the affected release branch.

Source: GitHub GHSA-jfgx-762w-99vr

Fix

@angular/common (npm): GitHub reports patched versions 20.3.34. Check the advisory for the affected release branch.

Source: GitHub GHSA-jfgx-762w-99vr

Fix

@angular/common (npm): OSV reports a fixed version 21.0.3. Check the advisory for supported release branches.

Source: OSV GHSA-jfgx-762w-99vr

Fix

@angular/common (npm): OSV reports a fixed version 20.3.34. Check the advisory for supported release branches.

Source: OSV GHSA-jfgx-762w-99vr

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
angular
angular
<= 19.2.25 (affected)
>= 20.0.0, < 20.3.34 (affected)
>= 21.0.0, < 21.0.3 (affected)
CNA: GitHub_M
@angular/common

@angular/common
npm
>= 21.0.0, < 21.0.3 (affected, GitHub advisory range) GitHub GHSA-jfgx-762w-99vr
@angular/common

@angular/common
npm
>= 20.0.0, < 20.3.34 (affected, GitHub advisory range) GitHub GHSA-jfgx-762w-99vr
@angular/common

@angular/common
npm
<= 19.2.25 (affected, GitHub advisory range) GitHub GHSA-jfgx-762w-99vr
@angular/common

@angular/common
npm
≥ 21.0.0; < 21.0.3 (affected, semver); OSV events: introduced 21.0.0; fixed 21.0.3
Source events (semver)
[
  {
    "introduced": "21.0.0"
  },
  {
    "fixed": "21.0.3"
  }
]

Other versions: unaffected
OSV GHSA-jfgx-762w-99vr
@angular/common

@angular/common
npm
≥ 20.0.0; < 20.3.34 (affected, semver); OSV events: introduced 20.0.0; fixed 20.3.34
Source events (semver)
[
  {
    "introduced": "20.0.0"
  },
  {
    "fixed": "20.3.34"
  }
]

Other versions: unaffected
OSV GHSA-jfgx-762w-99vr
@angular/common

@angular/common
npm
≥ 0; ≤ 19.2.25 (affected, semver); OSV events: introduced 0; last affected 19.2.25
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "last_affected": "19.2.25"
  }
]

Other versions: unaffected
OSV GHSA-jfgx-762w-99vr

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
4.0 / 5.9
medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCNA: GitHub_M
4.0 / 5.9
medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide