ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-111753

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

Published Oct 20, 2026 · catalog updated Oct 20, 2026 · @angular/common: XSRF Token Leakage

Last checked Nov 3, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-111753. A missing EPSS score is not a low risk. Compare @angular/common: XSRF Token Leakage with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (@angular/common: XSRF Token Leakage).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Version ranges on file
Affected products
npm @angular/common · package npm

An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) ( ) in 's HTTP Client ( ) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description To address , introduced a regular expression ( ) to detect and skip absolute and protocol-relative URLs before attaching the header. However, browsers resolve request URLs passed to and using the **WHATWG URL parser**. For and schemes, the WHATWG URL standard performs several normalizations prior to resolving the authority/origin: * Backslashes ( ) are treated as forward slashes ( ) — e.g., , , , , . * Leading and trailing C0 control characters and spaces ( ) are stripped — e.g., , , . * ASCII tab ( ), newline ( ), and carriage return ( ) characters are removed anywhere in the input — e.g., , , . Because these URLs do not match , treats them as relative same-origin URLs and attaches the header, while the browser resolves and dispatches the request to the cross-origin host ( ). Note: Angular and replaced the regular expression with a WHATWG origin comparison in [#65683](https://github.com/angular/angular/pull/65683) and were already unaffected. However, the LTS branch retained the regular expression until . ### Impact The token leakage bypasses Angular's built-in XSRF protection on affected versions, allowing an attacker to capture the user's valid header if their server permits the request and custom header via CORS. Once obtained, the attacker can perform Cross-Site Request Forgery (CSRF) attacks against the victim user's session. ### Attack Preconditions 1. The victim's Angular application must have **XSRF protection enabled** (enabled by default in ). 2. The attacker must be able to make the application send a state-changing HTTP request (e.g., , , , ) to a URL they cont

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @angular/common<= 19.2.25
  • npm @angular/common>= 20.0.0, < 20.3.34
  • npm @angular/common>= 21.0.0, < 21.0.3
  • package npmversion unspecified

How to fix CVE-2026-111753

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-111753. A missing EPSS score is not a low risk. Compare @angular/common: XSRF Token Leakage with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with <= 19.2.25, >= 20.0.0, < 20.3.34, >= 21.0.0, < 21.0.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-201; CWE-359. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Angular security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 20, 2026 · GitHub Advisory Database

    Detected

    An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) ( ) in 's HTTP Client ( ) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description

  2. Oct 20, 2026 · GitHub Advisory Database

    Updated

    An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) ( ) in 's HTTP Client ( ) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description

Sources

  • CVE.orgVulnerability recordCVE-2026-111753

    CVE.org record is not available yet.

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-jfgx-762w-99vr

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

    github.com
  • Maintainer security tabsVendor advisoryGHSA-jfgx-762w-99vr

    An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) ( ) in 's HTTP Client ( ) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description

    github.com
  • Snyk Vulnerability DatabasePackage advisorySNYK-JS-ANGULARCOMMON-21369526

    Exposure of Private Personal Information to an Unauthorized Actor

    security.snyk.io

References

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026
  • CVE.orgOct 23, 2026
  • Snyk Vulnerability DatabaseOct 23, 2026
  • GitHub Advisory DatabaseOct 21, 2026