vulns.co
/
GKData.io MCP and API Buy me a coffee

Angular

Angular host bindings: bind sanitization to the concrete output element

Angular could choose the wrong sanitization rules for the element receiving a directive's value. Its CVE-2026-88057 advisory explains that the rules came from the compile-time selector, so reuse or composition could leave a more sensitive element with weaker protection. The maintainer confirms a risk of browser script execution when an attacker controls that value; the sources do not establish a production compromise.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Treat element identity and output context as part of a binding's security contract. Re-evaluate that contract when composition, inheritance or dynamic construction changes the receiving element. The maintainer lists 22.1.0, 21.2.20 and 20.3.28 as patched; older end-of-support branches receive no patch. The researcher issue distinguishes ordinary URL, resource-loading and HTML contexts, so a generic URL filter is not evidence that all contexts are secured.

Before reading

  • Framework component composition and template binding concepts
  • Basic browser output-context and sanitization concepts

Context and limits

  • Exposure depends on attacker-influenced values reaching affected security-sensitive host bindings and a mismatch between compile-time and concrete-element context. Composition alone does not prove exploitability.
  • SkyZeroZx published the linked issue on June 27, 2026; the advisory credits SkyZeroZx as Remediation developer, and alan-agius4, josephperrott and JeanMeche as Remediation reviewers. GitHub identifies alan-agius4 as the publishing account. The reviewed advisory has no explicit narrative byline, so authors is empty; publication and remediation credits do not by themselves establish who wrote the narrative. The August 18 date describes the selected maintainer publication, not the earliest public discussion or a product release.
  • The maintainer suggests explicit sanitization or safe-scheme restriction as workarounds. Their applicability depends on the actual sink; the reviewed issue identifies stricter resource-loading and HTML contexts. This caveat is editorial defensive guidance, not a claim that the maintainer workaround was independently tested.
  • The issue explains a minimal case but links its runnable reproduction elsewhere. No reproduction was run, and observed exploit outcomes are not independently established.

Sources

  1. Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compilerAngular · reviewed 2026-10-03
  2. ResourceURL sanitizer bypass through host-binding selector mismatchSkyZeroZx · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software