CVE-2026-88057: Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: @angular/compiler (npm) 20.3.28, 21.2.20, 22.1.0; @angular/core (npm) 20.3.28, 21.2.20, 22.1.0.
Low priority for now. Upgrade to @angular/compiler (npm) 20.3.28, 21.2.20, 22.1.0; @angular/core (npm) 20.3.28, 21.2.20, 22.1.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.0, Angular's compiler and runtime in @angular/core and @angular/compiler could omit or select an incorrect sanitizer for security-sensitive directive host bindings because SecurityContext was derived from the declaring directive or component selector rather than the concrete host element. The mismatch is reachable through hostDirectives composition, inherited HostBinding declarations, createComponent with a custom hostElement or dynamic directives, SVG/MathML namespace elements, and tag-neutral selectors such as :not(...). Attacker-controlled href, src, action, xlink:href, or data values can therefore reach DOM attributes without Angular's built-in sanitizer and execute arbitrary JavaScript in the user's browser context. Applications unable to upgrade can use DomSanitizer.sanitize with SecurityContext.URL before assignment or restrict inputs to validated HTTP and HTTPS URL schemes. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.0.
- Published
- Sep 10, 2026
- Updated
- Sep 29, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-79
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is the Angular on your site affected?Scan JavaScript libraries
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| angular | angular | cpe:2.3:a:angular:angular |
Is the Angular on your site affected?
The free JavaScript library scanner reads the Angular version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.
Scan JavaScript librariesVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
angular angular
- <= 19.2.25, >= 20.0.0, < 20.3.28, >= 21.0.0, < 21.2.20, >= 22.0.0, < 22.1.0affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- angular angular19.0.0 and later · up to 19.2.25 inclusive
- angular angular20.0.0 and later · before 20.3.28
- angular angular21.0.0 and later · before 21.2.20
- angular angular22.0.0 and later · before 22.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | angular.js | from 0 | — |
| npm | @angular/compiler | from 20.0.0 · before 20.3.28 | 20.3.28 |
| npm | @angular/compiler | from 21.0.0 · before 21.2.20 | 21.2.20 |
| npm | @angular/compiler | from 22.0.0 · before 22.1.0 | 22.1.0 |
| npm | @angular/compiler | up to and including 19.2.25 | — |
| npm | @angular/core | from 20.0.0 · before 20.3.28 | 20.3.28 |
| npm | @angular/core | from 21.0.0 · before 21.2.20 | 21.2.20 |
| npm | @angular/core | from 22.0.0 · before 22.1.0 | 22.1.0 |
| npm | @angular/core | up to and including 19.2.25 | — |
Same product
angular: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-68945Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning35Monitor
- CVE-2026-50168Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass35Monitor
- CVE-2026-46417Angular: SSRF via Hostname Hijacking in @angular/platform-server35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-69151Aug 3, 2026 · Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes30Monitor
- ← EarlierCVE-2026-88056Sep 10, 2026 · Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR34Monitor
- Later →CVE-2026-88058Sep 10, 2026 · Angular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:@angular/compiler | 20.3.28 | Package registry (OSV) |
| npm:@angular/compiler | 21.2.20 | Package registry (OSV) |
| npm:@angular/compiler | 22.1.0 | Package registry (OSV) |
| npm:@angular/core | 20.3.28 | Package registry (OSV) |
| npm:@angular/core | 21.2.20 | Package registry (OSV) |
| npm:@angular/core | 22.1.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-880580 days apartAngular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements34Monitor
- CVE-2026-880600 days apartAngular: SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements34Monitor
- CVE-2026-6914938 days apartAngular SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)34Monitor
- CVE-2026-5055580 days apartAngular: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in @angular/platform-server34Monitor
- CVE-2026-5055680 days apartAngular: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR34Monitor
- CVE-2026-5426780 days apartAngular Client Hydration DOM Clobbering & Response-Cache Poisoning34Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/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:X
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/angular/angular/commit/6afe6fa781c2f0931f0aedd729b9884a8fe212ee
- github.com/angular/angular/commit/6caa298dee58319b2d674dc91364e26ffe3ecb2b
- github.com/angular/angular/issues/69550
- github.com/angular/angular/pull/69558
- github.com/angular/angular/releases/tag/v20.3.28
- github.com/angular/angular/releases/tag/v21.2.20
- github.com/angular/angular/releases/tag/v22.1.0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.