Skip to main content
VulnerabilityPublished Updated

CVE-2026-88057: Angular.js · 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

Affects angular.jsSource GCVE Database

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npm@angular/coreAffected
  • <=19.2.25
Fixed in–
npm@angular/compilerAffected
  • <=19.2.25
Fixed in–
Ubuntu:Pro:16.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=esm-infra/xenialOther threatsAffected
  • =1.2.28-1ubuntu2
  • =1.2.28-1ubuntu2+esm1
Fixed in–
Ubuntu:Pro:18.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=esm-infra/bionicOther threatsAffected
  • =1.5.10-1
  • =1.5.10-1ubuntu0.1~esm1
Fixed in–
Ubuntu:Pro:20.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=esm-apps/focalOther threatsAffected
  • =1.5.10-1
  • =1.7.9-1
  • =1.7.9-1ubuntu0.1~esm1
Fixed in–
Ubuntu:22.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=jammyOther threatsAffected
  • =1.8.2-2
  • =1.8.2-2ubuntu0.1
Fixed in–
Ubuntu:24.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=nobleOther threatsAffected
  • =1.8.3-1
  • =1.8.3-1ubuntu0.24.04.1
Fixed in–
Ubuntu:26.10angular.jspkg:deb/ubuntu/angular.js?arch=source&distro=stonkingOther threatsAffected
  • =1.8.3-3
Fixed in–
Ubuntu:26.04:LTSangular.jspkg:deb/ubuntu/angular.js?arch=source&distro=resoluteOther threatsAffected
  • =1.8.3-3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Official patches are available in Angular versions 20.3.28, 21.2.20, and 22.1.0. Users should upgrade to these or later versions to remediate the vulnerability. As a workaround, users are advised to explicitly sanitize inputs or restrict URL schemes to prevent injection of malicious content. Since this is a code-level vulnerability, applying the official fixes is the recommended mitigation.

Description

A vulnerability in Angular's @angular/core and @angular/compiler prior to versions 20.3.28, 21.2.20, and 22.1.0 allows sanitization bypass via directive host bindings on certain host elements. The Angular compiler incorrectly determines the security context based on the directive or component selector instead of the actual host element, potentially allowing untrusted inputs such as javascript: URLs to be inserted into DOM attributes without proper sanitization. This can enable Cross-Site Scripting (XSS) attacks. Official patches are available in the specified versions. Users are advised to explicitly sanitize inputs or restrict URL schemes as a workaround.

References

Community reviews

Loading reviews…