fix(deps, frontend): update dependency @angular/compiler to v21.2.20 - #8493
fix(deps, frontend): update dependency @angular/compiler to v21.2.20#8493renovate-bot wants to merge 1 commit into
Conversation
Backport auto-label reportThis
|
Automated Reviewer SuggestionsBased on the
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8493 +/- ##
============================================
+ Coverage 93.69% 93.87% +0.18%
Complexity 4826 4826
============================================
Files 1209 1209
Lines 49871 52114 +2243
Branches 6099 6679 +580
============================================
+ Hits 46727 48923 +2196
- Misses 1652 1677 +25
- Partials 1492 1514 +22
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This PR contains the following updates:
21.2.19→21.2.20Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
CVE-2026-88057 / GHSA-hh8m-fm6v-7cvg
More information
Details
Angular automatically sanitizes untrusted values bound to security-sensitive DOM sinks (such as
href,src,action,xlink:href, anddata) to protect against Cross-Site Scripting (XSS).Prior to the fix, the Angular compiler determined the
SecurityContextfor 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:
hostDirectivescomposition,createComponentwith customhostElementor 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.021.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://).Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
CVE-2026-88057 / GHSA-hh8m-fm6v-7cvg
More information
Details
Angular automatically sanitizes untrusted values bound to security-sensitive DOM sinks (such as
href,src,action,xlink:href, anddata) to protect against Cross-Site Scripting (XSS).Prior to the fix, the Angular compiler determined the
SecurityContextfor 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:
hostDirectivescomposition,createComponentwith customhostElementor 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.021.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://).Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
angular/angular (@angular/compiler)
v21.2.20Compare Source
core
http
Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.