cve.bz

CVE-2026-111753

5.9 mediumEPSS 0.5%Fix available

Medium (5.9) in angular angular. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @angular/common 20.3.34, 21.0.3.

On this page
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.

Severity

CVSS 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
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-359 Exposure of Private Personal Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-111753 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111753?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111753?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111753 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
angular<= 19.2.25
angular>= 20.0.0, < 20.3.34
angular>= 21.0.0, < 21.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jfgx-762w-99vrnpm@angular/common>=21.0.0 <21.0.321.0.3
GHSA-jfgx-762w-99vrnpm@angular/common>=20.0.0 <20.3.3420.3.34
GHSA-jfgx-762w-99vrnpm@angular/common<=19.2.25no fix published

Attack patterns (CAPEC)

  • CAPEC-464 Evercookie Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low
  • CAPEC-498 Probe iOS Screenshots
  • CAPEC-508 Shoulder Surfing Likelihood: High · Severity: High
  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-201.

References

Check your stackJSON