p PatchFirst

CVE-2026-88057

CVE-2026-88057 · Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 5.3 · Medium · EPSS 0.4% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • angular

    Versions
    • <= 19.2.25: Affected
    • >= 20.0.0, < 20.3.28: Affected
    • >= 21.0.0, < 21.2.20: Affected
    • >= 22.0.0, < 22.1.0: Affected

    No fix published

  • angular.js Debian:12

    Versions
    • 1.8.3-1
    • 1.8.3-1+deb12u1
    • 1.8.3-1+deb12u1~deb11u1
    • 1.8.3-2
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Debian:13

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • @angular/core npm

    Affected ranges
    • SEMVER: ≥ 22.0.0, < 22.1.0

    Update to 22.1.0

  • @angular/compiler npm

    Affected ranges
    • SEMVER: ≥ 22.0.0, < 22.1.0

    Update to 22.1.0

  • @angular/core npm

    Affected ranges
    • SEMVER: ≥ 21.0.0, < 21.2.20

    Update to 21.2.20

  • @angular/compiler npm

    Affected ranges
    • SEMVER: ≥ 21.0.0, < 21.2.20

    Update to 21.2.20

  • @angular/core npm

    Affected ranges
    • SEMVER: ≥ 20.0.0, < 20.3.28

    Update to 20.3.28

  • @angular/compiler npm

    Affected ranges
    • SEMVER: ≥ 20.0.0, < 20.3.28

    Update to 20.3.28

  • @angular/core npm

    Affected ranges
    • SEMVER: ≤ 19.2.25

    No fix published

  • @angular/compiler npm

    Affected ranges
    • SEMVER: ≤ 19.2.25

    No fix published

  • angular.js Ubuntu:Pro:16.04:LTS

    Versions
    • 1.2.28-1ubuntu2
    • 1.2.28-1ubuntu2+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:Pro:18.04:LTS

    Versions
    • 1.5.10-1
    • 1.5.10-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:Pro:20.04:LTS

    Versions
    • 1.5.10-1
    • 1.7.9-1
    • 1.7.9-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:22.04:LTS

    Versions
    • 1.8.2-2
    • 1.8.2-2ubuntu0.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:24.04:LTS

    Versions
    • 1.8.3-1
    • 1.8.3-1ubuntu0.24.04.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:26.10

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:26.04:LTS

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →