@angular/core
Affected
- introduced
22.0.0, fixed22.1.0(semver)
Fixed versions
22.1.0
Fix
- Fixed version
22.1.0npm install @angular/[email protected]
Advisory
Also known as: CVE-2026-88057
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
Angular automatically sanitizes untrusted values bound to security-sensitive DOM sinks (such as href, src, action, xlink:href, and data) to protect against Cross-Site Scripting (XSS).
Prior to the fix, the Angular compiler determined the SecurityContext for directive host bindings (host: {'[attr.href]': 'value'} or @HostBinding('attr.href')) based solely on the declaring directive or component selector at compile time, rather than the concrete host element that the directive was applied to.
When a directive with a security-sensitive host binding was applied to a different concrete host element—such as through:
hostDirectives composition,createComponent with custom hostElement or dynamic directives),<svg:a>, <math>), or:not(...)),the compiler either failed to associate a sanitizer with the host binding or attached an incorrect security context. As a result, untrusted inputs (e.g. javascript:... URLs) bound via the host binding would be written to the DOM attribute without passing through Angular's built-in sanitizer.
Impact
An attacker capable of controlling the value bound to an affected directive host binding could execute arbitrary JavaScript in the user's browser context (Cross-Site Scripting).
Patches
This issue has been resolved in versions:
22.1.0 21.2.2020.3.28Workarounds
Ensure that any user-controlled values assigned to properties bound via directive host bindings are explicitly sanitized using DomSanitizer.sanitize(SecurityContext.URL, ...) before assignment, or restrict the input to validated safe URL schemes (e.g. http://, https://).
Medium Basis: The source's own band: MODERATE
22.0.0, fixed 22.1.0 (semver)22.1.0
22.1.0npm install @angular/[email protected]22.0.0, fixed 22.1.0 (semver)22.1.0
22.1.0npm install @angular/[email protected]21.0.0, fixed 21.2.20 (semver)21.2.20
21.2.20npm install @angular/[email protected]21.0.0, fixed 21.2.20 (semver)21.2.20
21.2.20npm install @angular/[email protected]20.0.0, fixed 20.3.28 (semver)20.3.28
20.3.28npm install @angular/[email protected]20.0.0, fixed 20.3.28 (semver)20.3.28
20.3.28npm install @angular/[email protected]0, last affected 19.2.25 (semver)None listed
No fixed version is listed.
0, last affected 19.2.25 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0