Skip to content

chore(deps): update dependency @angular/core to v20.3.16 [security]#3659

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-angular-core-vulnerability
Open

chore(deps): update dependency @angular/core to v20.3.16 [security]#3659
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-angular-core-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2026

This PR contains the following updates:

Package Change Age Confidence
@angular/core (source) 20.3.1020.3.16 age confidence

GitHub Vulnerability Alerts

CVE-2026-22610

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context.

In a standard security model, attributes that can load and execute code (like a script's source) should be strictly validated. However, because the compiler does not classify these specific SVG attributes correctly, it allows attackers to bypass Angular's built-in security protections.

When template binding is used to assign user-controlled data to these attributes for example, <script [attr.href]="userInput"> the compiler treats the value as a standard string or a non-sensitive URL rather than a resource link. This enables an attacker to provide a malicious payload, such as a data:text/javascript URI or a link to an external malicious script.

Impact

When successfully exploited, this vulnerability allows for arbitrary JavaScript execution within the context of the victim's browser session. This can lead to:

  • Session Hijacking: Stealing session cookies, localStorage data, or authentication tokens.
  • Data Exfiltration: Accessing and transmitting sensitive information displayed within the application.
  • Unauthorized Actions: Performing state-changing actions (like clicking buttons or submitting forms) on behalf of the authenticated user.

Attack Preconditions

  1. The victim application must explicitly use SVG <script> elements within its templates.
  2. The application must use property or attribute binding (interpolation) for the href or xlink:href attributes of those SVG scripts.
  3. The data bound to these attributes must be derived from an untrusted source (e.g., URL parameters, user-submitted database entries, or unsanitized API responses).

Patches

  • 19.2.18
  • 20.3.16
  • 21.0.7
  • 21.1.0-rc.0

Workarounds

Until the patch is applied, developers should:

  • Avoid Dynamic Bindings: Do not use Angular template binding (e.g., [attr.href]) for SVG <script> elements.
  • Input Validation: If dynamic values must be used, strictly validate the input against a strict allowlist of trusted URLs on the server side or before it reaches the template.

Resources


Release Notes

angular/angular (@​angular/core)

v20.3.16

Compare Source

core
Commit Type Description
c2c2b4aaa8 fix sanitize sensitive attributes on SVG script elements

v20.3.15

Compare Source

compiler
Commit Type Description
d1ca8ae043 fix prevent XSS via SVG animation attributeName and MathML/SVG URLs

v20.3.14

Compare Source

http
Commit Type Description
0276479e7d fix prevent XSRF token leakage to protocol-relative URLs

v20.3.13

Compare Source

v20.3.12

Compare Source

v20.3.11

Compare Source

common
Commit Type Description
5047849a4a fix remove placeholder image listeners once view is removed
compiler
Commit Type Description
f9d0818087 fix support arbitrary nesting in :host-context()
106b9040df fix support commas in :host() argument
9419ea348a fix support complex selectors in :nth-child()
036c5d2a07 fix support one additional level of nesting in :host()
core
Commit Type Description
dcdd1bcdbb fix skip leave animations on view swaps

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Jan 9, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/animations@20.3.10
npm error Found: @angular/core@20.3.16
npm error node_modules/@angular/core
npm error   dev @angular/core@"20.3.16" from the root project
npm error   peer @angular/core@">=16.0.0" from @acrodata/code-editor@0.5.1
npm error   node_modules/@acrodata/code-editor
npm error     @acrodata/code-editor@"0.5.1" from the root project
npm error   14 more (@angular-devkit/build-angular, @angular/build, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"20.3.10" from @angular/animations@20.3.10
npm error node_modules/@angular/animations
npm error   dev @angular/animations@"20.3.10" from the root project
npm error   peerOptional @angular/animations@"20.3.10" from @angular/platform-browser@20.3.10
npm error   node_modules/@angular/platform-browser
npm error     dev @angular/platform-browser@"20.3.10" from the root project
npm error     9 more (@angular-devkit/build-angular, @angular/build, ...)
npm error   2 more (ngx-bootstrap, ngx-ui-switch)
npm error
npm error Conflicting peer dependency: @angular/core@20.3.10
npm error node_modules/@angular/core
npm error   peer @angular/core@"20.3.10" from @angular/animations@20.3.10
npm error   node_modules/@angular/animations
npm error     dev @angular/animations@"20.3.10" from the root project
npm error     peerOptional @angular/animations@"20.3.10" from @angular/platform-browser@20.3.10
npm error     node_modules/@angular/platform-browser
npm error       dev @angular/platform-browser@"20.3.10" from the root project
npm error       9 more (@angular-devkit/build-angular, @angular/build, ...)
npm error     2 more (ngx-bootstrap, ngx-ui-switch)
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/2026-02-02T17_57_58_021Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T17_57_58_021Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency @angular/core to v20.3.16 [security] chore(deps): update dependency @angular/core to v20.3.16 [security] - autoclosed Jan 10, 2026
@renovate renovate bot closed this Jan 10, 2026
@renovate renovate bot deleted the renovate/npm-angular-core-vulnerability branch January 10, 2026 12:40
@renovate renovate bot changed the title chore(deps): update dependency @angular/core to v20.3.16 [security] - autoclosed chore(deps): update dependency @angular/core to v20.3.16 [security] Jan 11, 2026
@renovate renovate bot reopened this Jan 11, 2026
@renovate renovate bot force-pushed the renovate/npm-angular-core-vulnerability branch 13 times, most recently from 5ffee4f to 4891977 Compare January 18, 2026 11:04
@renovate renovate bot force-pushed the renovate/npm-angular-core-vulnerability branch from 4891977 to 9ef4b11 Compare January 19, 2026 18:03
@renovate renovate bot force-pushed the renovate/npm-angular-core-vulnerability branch from 9ef4b11 to 17e32a7 Compare February 2, 2026 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants