Skip to content
major vulnerability· requires attention

Affects a widely used web framework; XSS could affect many sites across industries.

Web

CVE-2026-32635

8.6
High
EPSS 0.34%Patch availableMar 16, 2026

Angular XSS via i18n attribute bypass enables script injection.

common questions

Is CVE-2026-32635 being exploited?

Not confirmed. CVE-2026-32635 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-32635?

CVE-2026-32635 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-32635?

Yes. A fix has been recorded for CVE-2026-32635. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-32635 affect?

CVE-2026-32635 affects Angular runtime and compiler < 22.0.0-next.3; versions 21.2.4, 20.3.18, 19.2.20. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-32635?

Upgrade to 22.0.0-next.3 or newer; audit i18n usage; verify dependencies.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Angular runtime and compiler < 22.0.0-next.3; versions 21.2.4, 20.3.18, 19.2.20
impact

Allows attacker to inject/execute scripts in Angular apps via i18n bypass, risking data theft and session hijacking.

action required

Patch when possible

affected versions
@angular compiler
  • affected>= 22.0.0-next.0 and < 22.0.0-next.3
  • affected>= 21.0.0-next.0 and < 21.2.4
  • affected>= 20.0.0-next.0 and < 20.3.18
  • affected>= 17.0.0.next.0 and < 19.2.20
@angular core
  • affected>= 22.0.0-next.0 and < 22.0.0-next.3
  • affected>= 21.0.0-next.0 and < 21.2.4
  • affected>= 20.0.0-next.0 and < 20.3.18
  • affected>= 17.0.0.next.0 and < 19.2.20

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free