For your digest
@angular/core: @angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
@angular/core (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- @angular/core (npm): from 21.0.0-next.0, before 21.2.15
- @angular/core (npm): from 22.0.0-next.0, before 22.0.0-rc.2
- @angular/core (npm): from 19.0.0-next.0, before 19.2.23
- @angular/core (npm): every version, up to and including 18.2.14
- @angular/core (npm): from 20.0.0-next.0, before 20.3.22
The fix
@angular/core (npm) fixed in 21.2.15
npmnpm install "@angular/core@21.2.15"pnpmpnpm add "@angular/core@21.2.15"yarnyarn add "@angular/core@21.2.15"bunbun add "@angular/core@21.2.15"Check what is installednpm ls @angular/corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @angular/core to 21.2.15 or the nearest later release, to fix CVE-2026-52725. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@angular/core (npm) fixed in 22.0.0-rc.2
npmnpm install "@angular/core@22.0.0-rc.2"pnpmpnpm add "@angular/core@22.0.0-rc.2"yarnyarn add "@angular/core@22.0.0-rc.2"bunbun add "@angular/core@22.0.0-rc.2"Check what is installednpm ls @angular/corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @angular/core to 22.0.0-rc.2 or the nearest later release, to fix CVE-2026-52725. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@angular/core (npm) fixed in 19.2.23
npmnpm install "@angular/core@19.2.23"pnpmpnpm add "@angular/core@19.2.23"yarnyarn add "@angular/core@19.2.23"bunbun add "@angular/core@19.2.23"Check what is installednpm ls @angular/corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @angular/core to 19.2.23 or the nearest later release, to fix CVE-2026-52725. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@angular/core (npm) fixed in 20.3.22
npmnpm install "@angular/core@20.3.22"pnpmpnpm add "@angular/core@20.3.22"yarnyarn add "@angular/core@20.3.22"bunbun add "@angular/core@20.3.22"Check what is installednpm ls @angular/corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @angular/core to 20.3.22 or the nearest later release, to fix CVE-2026-52725. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".