CVE-2026-111753

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-117786 (ENISA EUVD) · GHSA-jfgx-762w-99vr (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 20, 2026

Last Modified

November 12, 2026

Advisory Details (8)

Auto-updated Nov 9, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

20.3.34

Patch available: angular/angular v20.3.34

https://github.com/angular/angular/releases/tag/v20.3.34
GitHub release Patch Available

21.0.3

Patch available: angular/angular 21.0.3

https://github.com/angular/angular/releases/tag/21.0.3
GitHub commit Patch Available

commit 933ce817d53e (angular/angular)

Patch available: angular/angular v20.3.34 (contains commit 933ce817d53e)

https://github.com/angular/angular/commit/933ce817d53e25926844fa56af8230816763d08e
GitHub commit

commit 20474d3f0fd7 (angular/angular)

Fix landed in angular/angular commit 20474d3f0fd7 — awaiting tagged release

https://github.com/angular/angular/commit/20474d3f0fd7c64071add6e84acf720627e5c19b
GitHub pull request Patch Available

[Backport 20.3.X] fix(http): enable XSRF protection for same-origin absolute URLs

Patch available: angular/angular v20.3.34 (PR #71295 merged 2026-10-14)

https://github.com/angular/angular/pull/71295
GitHub pull request Patch Available

fix(http): enable XSRF protection for same-origin absolute URLs

Patch available: angular/angular v22.2.0-next.4 (PR #65683 merged 2025-12-03)

https://github.com/angular/angular/pull/65683
Web page

XSRF header is still sent to other origins on 20.3.x through backslash and whitespace URLs · Issue #71294 · angular/angular · GitHub

https://github.com/angular/angular/issues/71294
GitHub advisoryMentions a patch (unverified)

XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035) · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-jfgx-762w-99vr

Vendor Advisories for CVE-2026-111753(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/common @ 21.0.3 (fixes >= 21.0.0, < 21.0.3)—ghsa
npm@angular/common @ 20.3.34 (fixes >= 20.0.0, < 20.3.34)—ghsa
npm@angular/common—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/common—
  • 21.0.0 up to 21.0.3: fixed in 21.0.3
  • 20.0.0 up to 20.3.34: fixed in 20.3.34
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 16× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-12 22:31 UTCEchelonGraph re-scored
  3. 2026-11-12 22:31 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-11-11 06:40 UTCEchelonGraph re-scored
  7. 2026-11-11 06:40 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  8. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-09 23:48 UTCEchelonGraph re-scored
  10. 2026-11-09 23:48 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  11. 2026-11-09 22:55 UTCEchelonGraph re-scored
  12. 2026-11-09 22:55 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  13. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  15. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  17. 2026-11-05 21:30 UTCEchelonGraph re-scored
  18. 2026-11-05 21:30 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  19. 2026-11-05 20:27 UTCMITRE cvelistV5CVSS → 5.9 · CVSS v4 → 5.9
  20. 2026-11-05 20:27 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  21. 2026-11-05 20:27 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  22. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-jfgx-762w-99vr · GitHub severity MODERATE
  23. 2026-10-25 14:52 UTCEchelonGraph re-scored
  24. 2026-10-20 21:22 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-111753?
CVE-2026-111753 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. 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…
When was the CVE record for CVE-2026-111753 published?
The CVE record for CVE-2026-111753 was published on October 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-111753 actively exploited?
CVE-2026-111753 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111753?
CVE-2026-111753 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111753?
A fix for CVE-2026-111753 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111753 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-111753

Explore →

Is Your Infrastructure Affected by CVE-2026-111753?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs