fix(deps): update dependency @angular/compiler to v19.2.17 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@angular/compiler (source)	19.2.16 → 19.2.17

GitHub Vulnerability Alerts

CVE-2025-66412

A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts.

Additionally, a related vulnerability exists involving SVG animation elements (<animate>, <set>, <animateMotion>, <animateTransform>). The attributeName attribute on these elements was not properly validated, allowing attackers to dynamically target security-sensitive attributes like href or xlink:href on other elements. By binding attributeName to "href" and providing a javascript: URL in the values or to attribute, an attacker could bypass sanitization and execute arbitrary code.

Attributes confirmed to be vulnerable include:

• SVG-related attributes: (e.g., xlink:href), and various MathML attributes (e.g., math|href, annotation|href).
• SVG animation attributeName attribute when bound to "href" or "xlink:href".

When template binding is used to assign untrusted, user-controlled data to these attributes (e.g., [attr.xlink:href]="maliciousURL" or <animate [attributeName]="'href'" [values]="maliciousURL">), the compiler incorrectly falls back to a non-sanitizing context or fails to block the dangerous attribute assignment. This allows an attacker to inject a javascript:URL payload. Upon user interaction (like a click) on the element, or automatically in the case of animations, the malicious JavaScript executes in the context of the application's origin.

Impact

When exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables:

• Session Hijacking: Stealing session cookies and authentication tokens.
• Data Exfiltration: Capturing and transmitting sensitive user data.
• Unauthorized Actions: Performing actions on behalf of the user.

Patches

• 19.2.17
• 20.3.15
• 21.0.2

Attack Preconditions

• The victim's Angular application must render data derived from untrusted input (e.g., from a database or API) and bind it to one of the unsanitized URL attributes or the attributeName of an SVG animation element.
• The victim must perform a user interaction (e.g., clicking) on the compromised element for the stored script to execute, or the animation must trigger the execution.

Workarounds

If you cannot upgrade, you can workaround the issue by ensuring that any data bound to the vulnerable attributes is never sourced from untrusted user input (e.g., database, API response, URL parameters).

• Avoid Affected Template Bindings: Specifically avoid using template bindings (e.g., [attr.xlink:href]="maliciousURL") to assign untrusted data to the vulnerable SVG/MathML attributes.
• Avoid Dynamic attributeName on SVG Animations: Do not bind untrusted data to the attributeName attribute of SVG animation elements (<animate>, <set>, etc.).
• Enable Content Security Policy (CSP): Configure a robust CSP header that disallows javascript: URLs.

---

Release Notes

angular/angular (@​angular/compiler)

v19.2.17

Compare Source

compiler

Commit	Type	Description
7c42e2ebeb	fix	prevent XSS via SVG animation attributeName and MathML/SVG URLs

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: website/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/compiler-cli@19.2.16
npm error Found: @angular/compiler@19.2.17
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"19.2.17" from the root project
npm error   peer @angular/compiler@"^19.0.0 || ^19.2.0-next.0" from @angular/build@19.2.19
npm error   node_modules/@angular/build
npm error     @angular/build@"19.2.19" from @angular-devkit/build-angular@19.2.19
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler@"19.2.16" from @angular/compiler-cli@19.2.16
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"19.2.16" from the root project
npm error   peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0" from @angular-devkit/build-angular@19.2.19
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error   2 more (@angular/build, @ngtools/webpack)
npm error
npm error Conflicting peer dependency: @angular/compiler@19.2.16
npm error node_modules/@angular/compiler
npm error   peer @angular/compiler@"19.2.16" from @angular/compiler-cli@19.2.16
npm error   node_modules/@angular/compiler-cli
npm error     dev @angular/compiler-cli@"19.2.16" from the root project
npm error     peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0" from @angular-devkit/build-angular@19.2.19
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error     2 more (@angular/build, @ngtools/webpack)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-12-31T15_01_02_687Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-31T15_01_02_687Z-debug-0.log

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/compiler-cli@19.2.16
npm error Found: @angular/compiler@19.2.17
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"19.2.17" from the root project
npm error   peer @angular/compiler@"^19.0.0 || ^19.2.0-next.0" from @angular/build@19.2.19
npm error   node_modules/@angular/build
npm error     @angular/build@"19.2.19" from @angular-devkit/build-angular@19.2.19
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler@"19.2.16" from @angular/compiler-cli@19.2.16
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"19.2.16" from the root project
npm error   peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0" from @angular-devkit/build-angular@19.2.19
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error   3 more (@angular/build, @ngtools/webpack, ng-packagr)
npm error
npm error Conflicting peer dependency: @angular/compiler@19.2.16
npm error node_modules/@angular/compiler
npm error   peer @angular/compiler@"19.2.16" from @angular/compiler-cli@19.2.16
npm error   node_modules/@angular/compiler-cli
npm error     dev @angular/compiler-cli@"19.2.16" from the root project
npm error     peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0" from @angular-devkit/build-angular@19.2.19
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"19.2.19" from the root project
npm error     3 more (@angular/build, @ngtools/webpack, ng-packagr)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-12-31T15_01_12_266Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-31T15_01_12_266Z-debug-0.log