fix(deps): update dependency @angular/core to v20 [security] by renovate[bot] · Pull Request #125 · HugoMendes98/graph-flow

renovate · 2026-01-10T09:33:48Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@angular/core (source)	`^16.2.3` → `^20.0.0`

@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

CVE-2026-52725 / GHSA-692r-grfm-v8x7

More information

Details

An issue in the @angular/core package allows bypassing script-execution restrictions during dynamic component creation.

Specifically, the dynamic component instantiation mechanism (createComponent) failed to reject mounting components directly onto a <script> or namespaced script element (such as <svg:script>). This enabled the initialization of custom components on a tag that executes scripts, allowing attackers to hijack or inject script-executing hosts.

This flaw enables an attacker who can control the host element or selector parameter passed to createComponent to initialize or mount an Angular component directly onto a <script> tag, leading to execution of untrusted code or client-side Cross-Site Scripting (XSS).

Impact

Any Angular application that registers dynamic components based on user-supplied parameters (like selectors or host elements) is vulnerable to this security bypass.

Once exploited, this allows a malicious actor to mount a dynamic component on a script tag, bypassing core dynamic component creation safeguards to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.

Attack Preconditions

To successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:

User-Controlled Host Selection: The application must accept user-controlled inputs that are passed as a selector/host element to createComponent.
Absence of Additional Context Sanitization: The application does not perform separate input sanitization before feeding values to the dynamic creation APIs.

Patches

22.0.0-rc.2
21.2.15
20.3.22
19.2.23

Severity

CVSS Score: 5.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Angular: Template and Attribute Namespace Sanitization Bypass (XSS)

CVE-2026-50557 / GHSA-f3m7-gqxr-g87x

More information

Details

An issue in the @angular/compiler and @angular/core packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds.

Specifically, namespaced script elements (e.g., <svg:script> or <:svg:script>) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped.

Furthermore, security context schema mappings for element attributes did not consistently handle attributes within namespaced elements (like SVG and MathML), opening up gaps where malicious namespaced attributes could bypass runtime and compile-time sanitizers.

Combined, these flaws enable an attacker who can inject or supply a template/tag structure with custom namespaces to bypass Angular's script-stripping logic and attribute sanitizers, leading to client-side Cross-Site Scripting (XSS).

Impact

Any Angular application that compiles user-controlled templates at runtime, or relies on sanitization of namespaced elements/attributes, is vulnerable to this security bypass.

Once exploited, this allows a malicious actor to inject a namespaced script element or dynamic attribute bindings, bypassing core sanitization constraints to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.

Attack Preconditions

To successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:

User-Controlled Template Input: The application must accept user-controlled inputs that are directly processed by the Angular template compiler at runtime.
Namespace Parsing Support: The input structure must employ custom namespace prefixes (such as <svg:script>) to evade standard tag-name blocklists/checks.
Absence of Additional Context Sanitization: The application does not perform separate input sanitization before feeding values to the Angular compiler.

Patches

22.0.0-rc.2
21.2.15
20.3.22
19.2.23

Severity

CVSS Score: 5.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Angular i18n vulnerable to Cross-Site Scripting

CVE-2026-27970 / GHSA-prjf-86w9-mfqv

More information

Details

A Cross-site Scripting (XSS) vulnerability has been identified in the Angular internationalization (i18n) pipeline. In ICU messages (International Components for Unicode), HTML from translated content was not properly sanitized and could execute arbitrary JavaScript.

Angular i18n typically involves three steps, extracting all messages from an application in the source language, sending the messages to be translated, and then merging their translations back into the final source code. Translations are frequently handled by contracts with specific partner companies, and involve sending the source messages to a separate contractor before receiving final translations for display to the end user.

If the returned translations have malicious content, it could be rendered into the application and execute arbitrary JavaScript.

Impact

When successfully exploited, this vulnerability allows for execution of attacker controlled JavaScript in the application origin. Depending on the nature of the application being exploited this could lead to:

Credential Exfiltration: Stealing sensitive user data stored in page memory, LocalStorage, IndexedDB, or cookies available to JS and sending them to an attacker controlled server.
Page Vandalism: Mutating the page to read or act differently than intended by the developer.

Attach Preconditions

The attacker must compromise the translation file (xliff, xtb, etc.).
Unlike most XSS vulnerabilities, this one is not exploitable by arbitrary users. An attacker must first compromise an application's translation file before they can escalate privileges into the Angular application client.
The victim application must use Angular i18n.
The victim application must use one or more ICU messages.
The victim application must render an ICU message.
The victim application must not defend against XSS via a safe Content-Security Policy (CSP) or Trusted Types.

Patches

21.2.0
21.1.6
20.3.17
19.2.19

Workarounds

Until the patch is applied, developers should consider:

Reviewing and verifying translated content received from untrusted third parties before incorporating it in an Angular application.
Enabling strict CSP controls to block unauthorized JavaScript from executing on the page.
Enabling Trusted Types to enforce proper HTML sanitization.

References

Fix

Severity

CVSS Score: 7.0 / 10 (High)
Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes

CVE-2026-69151 / GHSA-jj27-h5hq-8x99

More information

Details

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular compiler's internationalization (i18n) pipeline. Although Angular disallows binding to event-handler attributes such as onclick and onerror through standard attribute validation (validateAttribute() / validateProperty()), the i18n metadata collection path allowed these same attribute names to be marked for translation using i18n-on* attributes (e.g., i18n-onerror).

When exploited, a lower-trust translation file could replace a benign static handler such as onerror="void 0" with arbitrary executable JavaScript in the localized build.

The following example illustrates a vulnerable pattern:

<img src="foo.jpg" onerror="void 0" i18n-onerror />

Impact

When exploited, this vulnerability allows arbitrary JavaScript execution within the context of the vulnerable application's domain if an attacker can control or influence the translation files used during localization. This can lead to:

Session Hijacking: Accessing session cookies, tokens, or sensitive user data.
Unauthorized Actions: Performing actions on behalf of the authenticated user.

Patched Versions

22.0.1
21.2.19
20.3.27

Workarounds

Ensure that static event-handler attributes (e.g., onerror, onclick) are never marked for internationalization (i18n-on*) in application templates, and ensure translation files are sourced from trusted origins.

Severity

CVSS Score: 7.6 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

CVE-2026-54267 / GHSA-rgjc-h3x7-9mwg

More information

Details

To optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application's runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a <script> tag with a predictable identifier:

<script type="application/json" id="ng-state">
    {"some-api-url": {"body": ...}}
</script>

During client bootstrap, Angular recovers this state by looking up the element via document.getElementById('ng-state') and parsing its text content.

Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering.

If the application binds untrusted user input or CMS content to element properties such as id (e.g., <div [id]="userInput"> or <a id="ng-state">) before the genuine <script> tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup.

During hydration, when Angular calls document.getElementById('ng-state'), the browser returns the attacker's clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON.

Impact

By clobbering the state element, the attacker can inject a custom JSON payload into Angular's TransferState cache. The most critical exploitation vector is poisoning the HTTP Transfer Cache.

The attacker injects a clobbered ng-state element containing custom JSON.
The JSON maps a key (representing a target API endpoint URL) to a malicious payload of the attacker's choice.
During client-side initialization, Angular's HttpClient checks TransferState before making requests. Finding the poisoned key, HttpClient returns the forged response instantly instead of requesting the genuine backend API.

Depending on how the application processes and renders the affected API response, this can lead to:

DOM-based Cross-Site Scripting (XSS) if poisoned fields are rendered using unsafe bindings.
Privilege Escalation by spoofing user info or session details retrieved from poisoned API payloads.
UI Hijacking and redirection by spoofing configuration endpoints.

Patched Versions

22.0.1
21.2.17
20.3.25

Workarounds

If you cannot immediately update to a patched Angular version, apply the following workarounds:

A. Avoid Dynamic/User-Controlled IDs

Avoid binding raw user-supplied values or dynamic CMS IDs directly to element attributes. If dynamic IDs are required, sanitize them or prepend a static safe prefix:

<!-- Vulnerable Pattern -->
<div [id]="userControlledInput">...</div>

<!-- Mitigated Pattern -->
<div [id]="'safe-prefix-' + userControlledInput">...</div>

B. Configure a Custom Application ID

Declaring a unique, non-predictable APP_ID changes the ID suffix of the state element, making it harder for attackers to predict and target:

// app.config.ts

import { APP_ID } from '@angular/core';
import { provideClientHydration } from '@angular/platform-browser';

export const appConfig = {
  providers: [
    { provide: APP_ID, useValue: 'unique-obfuscated-app-id' },
    provideClientHydration()
  ]
};

This changes the state element lookup ID from ng-state to unique-obfuscated-app-id-state.

Severity

CVSS Score: 8.6 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Release Notes

angular/angular (@angular/core)

`v20.0.0`

Compare Source

Blog post: https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301

Breaking Changes

common

Using the Y formatter (week-numbering year) without also including w (week number) is now detected as suspicious date pattern, as y is typically intended.
AsyncPipe now directly catches unhandled errors in
subscriptions and promises and reports them to the application's
ErrorHandler. For Zone-based applications, these errors would have
been caught by ZoneJS and reported to ErrorHandler so the result is
generally the same. The change to the exact mechanism for reporting can
result in differences in test environments that will require test
updates.

compiler

'in' in an expression now refers to the operator
void in an expression now refers to the operator

Previously an expression in the template like {{void}} referred to a
property on the component class. After this change it now refers to the
void operator, which would make the above example invalid. If you have
existing expressions that need to refer to a property named void,
change the expression to use this.void instead: {{this.void}}.
Parenthesis are always respected.

This can lead to runtime breakages when a nullish coalescing operator is nested within parentheses.
eg. {{ (foo?.bar).baz }} will throw if foo is nullish. This is the same behavior as native JavaScript.

core

TypeScript versions less than 5.8 are no longer supported.
the TestBed.flushEffects() was removed - use
the TestBed.tick() instead.
provideExperimentalCheckNoChangesForDebug has several
breaking changes:
- It is renamed to provideCheckNoChangesConfig
- The behavior applies to all checkNoChanges runs
- The useNgZoneOnStable option is removed. This wasn't found to be generally
  more useful than interval
provideExperimentalZonelessChangeDetection is
renamed to provideZonelessChangeDetection as it is now "Developer
Preview" rather than "Experimental".
- InjectFlags has been removed.
- inject no longer accepts InjectFlags.
- Injector.get no longer accepts InjectFlags.
- EnvironmentInjector.get no longer accepts InjectFlags.
- TestBed.get no longer accepts InjectFlags.
- TestBed.inject no longer accepts InjectFlags.
- TestBed.get has been removed. Use TestBed.inject instead.
afterRender was renamed to afterEveryRender.
- Angular no longer supports Node.js v18.
- Node.js versions 22.0 to 22.10 are also no longer supported.
Before upgrading to Angular v20, ensure the Node.js version is at least 20.11.1.
For the full list of supported versions, visit: https://angular.dev/reference/versions
PendingTasks.run no longer returns the result of the
async function. If this behavior is desired, it can be re-implemented
manually with the PendingTasks.add. Be aware, however, that promise rejections
will need to be handled or they can cause the node process to shut down
when using SSR.
Uncaught errors in listeners which were previously only reported to
ErrorHandler are now also reported to Angular's internal error
handling machinery. For tests, this means that the error will be
rethrown by default rather than only logging the error. Developers
should fix these errors, catch them in the test if the test is
intentionally covering an error case, or use rethrowApplicationErrors: false in configureTestingModule as a last resort.
The any overload has been removed from
injector.get. It now only supports ProviderToken<T> and (deprecated
since v4) string.
Animations are guaranteed to be flushed when Angular
runs automatic change detection or manual calls to ApplicationRef.tick.
Prior to this change, animations would not be flushed in some situations
if change detection did not run on any views attached to the
application. This change can affect tests which may rely on the old
behavior, often by making assertions on DOM elements that should have
been removed but weren't because DOM removal is delayed until animations
are flushed.
ApplicationRef.tick will no longer catch and report
errors to the application ErrorHandler. Errors will instead be thrown out of
the method and will allow callers to determine how to handle these
errors, such as aborting follow-up work or reporting the error and
continuing.
This commit deprecates ng-reflect-* attributes and updates the runtime to stop producing them by default. Please refactor application and test code to avoid relying on ng-reflect-* attributes.

To enable a more seamless upgrade to v20, we've added the provideNgReflectAttributes() function (can be imported from the @angular/core package), which enables the mode in which Angular would be producing those attribites (in dev mode only). You can add the provideNgReflectAttributes() function to the list of providers within the bootstrap call.

router

The RedirectFn can now return Observable or
Promise. Any code that directly calls functions returning this type
may need to be adjusted to account for this.
Several methods in the public API of the Router which
required writable arrays have now been updated to accept readonly
arrays when no mutations are done.
The guards arrays on Route no longer include any in
the type union. The union includes functions for the functional guards
as well as a type matching Injector.get: ProviderToken<T>|string.
Note that string is still deprecated on both the route guards and
Injector.get.

Deprecations

core

ngIf/ngFor/ngSwitch are deprecated. Use the control flow blocks instead (@for/@if/@switch).

platform-browser

All entries of the @angular/platform-browser-dynamic
HammerJS support is deprecated and will be removed in a future major version.

platform-server

@angular/platform-server/testing

Use e2e tests to verify SSR behavior instead.

common

Commit	Type	Description
2e5362a469	feat	accept undefined inputs in NgTemplateOutlet (#61404)
b7d3f3dbfc	feat	Allow passing ScrollOptions to ViewportScroller (#61002)
74cceba587	feat	throw error for suspicious date patterns (#59798)
255c79e048	fix	cleanup `updateLatestValue` if view is destroyed before promise resolves (#58041)
739cadae62	fix	Handle errors in async pipe subscriptions (#60057)
cbbea70fa3	fix	issue a warning instead of an error when `NgOptimizedImage` exceeds the preload limit (#60879)
fc4a56d5c5	fix	rename httpResource function in factory (#60022)
785a1110e6	fix	resolve host binding type issues (#60481)

compiler

Commit	Type	Description
7a971766dc	feat	add extended diagnostic for uninvoked track function on `@for` blocks (#60495)
f2d5cf7edd	feat	support exponentiation operator in templates (#59894)
51b8ff23ce	feat	support tagged template literals in expressions (#59947)
1b8e7ab9fe	feat	support the `in` keyword in Binary expression (#58432)
0361c2d81f	feat	support void operator in templates (#59894)
8b990a31c3	fix	error if rawText isn't estimated correctly (#60529)
4fe489f1b4	fix	exponentiation should be right-to-left associative (#60101)
ef1fd137a9	fix	incorrect spans for template literals (#60323)
e0d378d20e	fix	incorrectly handling let declarations inside i18n (#60512)
b70ad3c4e6	fix	proper handling of typeof, void in RecursiveAstVisitor (#60101)
e25e6c95a2	fix	remove TypeScript from linker (#61635)
768239a89c	perf	reduce allocations for let declarations only used in the same view (#60512)

compiler-cli

Commit	Type	Description
bec1610da2	feat	add extended diagnostic for invalid nullish coalescing (#60279)
c889382a20	feat	detect missing structural directive imports (#59443)
1971e57a45	feat	support type checking of host bindings (#60267)
9ec9c7e1b8	fix	avoid fatal diagnostics for invalid module schemas (#61220)
a1cacc5b17	fix	avoid fatal diagnostics for missing template files (#58673)
1e6faad479	fix	correctly parse event name in HostListener (#60561)
ffb19e64f1	fix	preserve required parens for nullish coalescing (#60060)
7c9b4892e9	fix	preserve required parens in exponentiation expressions (#60101)
7e03af898e	fix	set correct target when type checking events (#60561)
2d51a203dc	fix	wrong event name for host listener decorators (#60460)

core

Commit	Type	Description
22d3f0562c	feat	add hook for producer creation side effects (#60333)
fe57332fc5	feat	add input binding support to dynamically-created components (#60137)
65adb3024d	feat	Add provider which reports unhandled errors on window to ErrorHandler (#60704)
b154fb3911	feat	add support for two-way bindings on dynamically-created components (#60342)
82aa2c1a52	feat	add the ability to apply directives to dynamically-created components (#60137)
326d48afb4	feat	drop support for TypeScript older than 5.8 (#60197)
d260ca3091	feat	emit template function for template related profiler hooks (#60174)
a4bad8d361	feat	export signalGetFn from signal primitives (#60497)
4812215a7b	feat	Expose `Injector.destroy` on `Injector` created with `Injector.create` (#60054)
c1bcae91dd	feat	expose performance data in Chrome DevTools (#60789)
809b5b4596	feat	introduce new DI profiling event (#60158)
d5fd7349fb	feat	introduce TestBed.tick() (#60993)
4e88e18a8e	feat	mark `toObservable` as stable (#60449)
727cda3856	feat	mark linkedSignal API as public (#60865)
644d9f3bbd	feat	mark the toSignal API as stable (#60442)
e711f99d81	feat	move `provideExperimentalCheckNoChangesForDebug` to `provideCheckNoChangesConfig` (#60906)
7ccec1494f	feat	move DOCUMENT token into core (#60663)
953c4b2580	feat	Move zoneless change detection to dev preview (#60748)
611baaf069	feat	remove InjectFlags from public API (#60318)
5e209cb560	feat	remove TestBed.get (#60414)
d8fbb909ce	feat	rename afterRender to afterEveryRender and stabilize (#60999)
567522398f	feat	stabilize incremental hydration api (#60888)
8d050b5bfc	feat	stabilize linkedSignal API (#60741)
866cea9a05	feat	Stabilize PendingTasks Injectable (#60716)
bf8492b871	feat	stabilize withI18nSupport() api (#60889)
be44cc8f40	feat	support listening to outputs on dynamically-created components (#60137)
fe9b79b615	feat	update Node.js version support (#60545)
e170d24240	fix	add migration away from InjectFlags (#60318)
7eb59d3887	fix	added @angular/compiler as a peer dependency (#55610)
7232ce5b17	fix	Catch and report rejections in async function of `PendingTasks.run` (#60044)
fd12220a35	fix	defer block render failures should report to application error handler (#60149)
3459faadbf	fix	do not allow setInput to be used with inputBinding (#60137)
0ac949c266	fix	do not run change detection on global error events (#60944)
4fe34f4cfe	fix	enable stashing only when `withEventReplay()` is invoked (#61077)
962b59b14e	fix	Ensure ComponentFixture does not duplicate error reporting from FakeAsync (#60104)
7b819be83f	fix	Ensure errors in listeners report to the application error handler (#60251)
ff772d7800	fix	fix typing on injector.get to omit 'any' (#60202)
13d1c8ab38	fix	fixes timing of hydration cleanup on control flow (#60425)
0b69b61929	fix	Flush animations when no component has been checked (#58089)
3ba39bc28f	fix	getting resource value throws an error instead of returning undefined (#61441)
ca6295e90b	fix	handle different DI token types in Chrome DevTools integration (#61333)
0162ceb427	fix	inject migration should treat `@Attribute` as optional (#60916)
ea5eb28865	fix	input targeting not checking if input exists on host (#60137)
c8951159ac	fix	mark `zone.js` as an optional peer dependency (#61616)
d62379bb13	fix	move reload method from Resource to WritableResource (#61441)
a89f1cff24	fix	narrow error type for resources API (#61441)
624be2ef0c	fix	prevent stash listener conflicts (#59635)
017cc0a37c	fix	properly handle app stabilization with defer blocks (#61040)
6e79eaf739	fix	reading resource value after reload in the error state (#61441)
3d85d9363c	fix	reduce total memory usage of various migration schematics (#60774)
1c7b356625	fix	release `hasPendingTasks` observers (#59723)
43cbc58254	fix	remove `forceRoot` flag for effects (#60535)
48974c3cf8	fix	remove `rejectErrors` option encourages uncaught exceptions (#60397)
491b0a4ead	fix	Remove duplicate reporting of errors in `CDR.detectChanges` (#60056)
04d963c0a5	fix	remove unused parameter from listener instruction (#60406)
0ae1889560	fix	run `ApplicationRef.prototype.bootstrap` in `NgZone` (#60720)
a611b234d7	fix	run root effects in creation order (#60534)
338818ce89	fix	Surface errors from `ApplicationRef.tick` to callsite (#60102)
350776b412	fix	TestBed.tick should ensure test components are synchronized (#61382)
3d4ddd2247	fix	Testing should not throw when Zone does not patch test FW APIs (#61628)
30e081287d	fix	update min Node.js support to 20.19, 22.12, and 24.0 (#61500)
b407157ee8	refactor	Deprecate the structural directives `ngIf`/`ngFor`/`ngSwitch`. (#60492)
c2987d8402	refactor	stop producing `ng-reflect` attributes by default (#60973)

forms

Commit	Type	Description
a07ee60989	feat	add markAllAsDirty to AbstractControl (#58663)
bdfbd54932	feat	Allow to reset a form without emitting events (#60354)
81fe0536fd	fix	Make sure statusChanges is emitted (#57098)
bdd5e20423	fix	resolve host binding type issues (#60481)

http

Commit	Type	Description
ccc5cc068f	feat	add keepalive support for fetch requests (#60621)
5795e03cdf	fix	Delay stabilization until next app synchronization (#60656)

platform-browser

Commit	Type	Description
bc2cab747f	refactor	Deprecate the `platform-browser-dynamic` package (#61043)
a980ac9a6a	refactor	Deprecate the HammerJS integration ([#60257](ht

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

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

♻ 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 · 2026-01-10T09:33:49Z

⚠️ 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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: graph-flow@0.6.4
npm error Found: @angular/compiler@16.2.3
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"^16.2.3" from the root project
npm error   peer @angular/compiler@"16.2.3" from @angular/compiler-cli@16.2.3
npm error   node_modules/@angular/compiler-cli
npm error     dev @angular/compiler-cli@"^16.2.3" from the root project
npm error     peer @angular/compiler-cli@"^16.0.0" from @angular-devkit/build-angular@16.2.1
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"^16.2.1" from the root project
npm error       3 more (@nx/angular, @storybook/angular, jest-preset-angular)
npm error     3 more (@ngtools/webpack, @storybook/angular, jest-preset-angular)
npm error   3 more (@angular/platform-browser-dynamic, ...)
npm error
npm error Could not resolve dependency:
npm error @angular/core@"^20.0.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/compiler@16.2.12
npm error node_modules/@angular/compiler
npm error   peerOptional @angular/compiler@"20.3.27" from @angular/core@20.3.27
npm error   node_modules/@angular/core
npm error     @angular/core@"^20.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-07-30T20_41_27_004Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-30T20_41_27_004Z-debug-0.log

renovate Bot added dependencies renovate security labels Jan 10, 2026

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security]~~ fix(deps): update dependency @angular/core to v19 [security] - autoclosed Feb 18, 2026

renovate Bot closed this Feb 18, 2026

renovate Bot deleted the renovate/npm-angular-core-vulnerability branch February 18, 2026 05:38

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security] - autoclosed~~ fix(deps): update dependency @angular/core to v19 [security] Feb 18, 2026

renovate Bot reopened this Feb 18, 2026

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch 2 times, most recently from 2d54dd9 to fda2533 Compare February 18, 2026 10:36

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security]~~ fix(deps): update dependency @angular/core to v19 [security] - autoclosed Feb 25, 2026

renovate Bot closed this Feb 25, 2026

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security] - autoclosed~~ fix(deps): update dependency @angular/core to v19 [security] Feb 25, 2026

renovate Bot reopened this Feb 25, 2026

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch 2 times, most recently from fda2533 to 35fee92 Compare February 25, 2026 21:17

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security]~~ fix(deps): update dependency @angular/core to v19 [security] - autoclosed Mar 29, 2026

renovate Bot closed this Mar 29, 2026

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security] - autoclosed~~ fix(deps): update dependency @angular/core to v19 [security] Mar 29, 2026

renovate Bot reopened this Mar 29, 2026

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch 2 times, most recently from 35fee92 to e673b60 Compare March 29, 2026 08:43

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security]~~ fix(deps): update dependency @angular/core to v19 [security] - autoclosed May 8, 2026

renovate Bot closed this May 8, 2026

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security] - autoclosed~~ fix(deps): update dependency @angular/core to v19 [security] May 8, 2026

renovate Bot reopened this May 8, 2026

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch 2 times, most recently from e673b60 to 70c634f Compare May 8, 2026 20:39

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch from 70c634f to 2dd317f Compare July 16, 2026 00:40

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v19 [security]~~ fix(deps): update dependency @angular/core to v20 [security] Jul 16, 2026

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v20 [security]~~ fix(deps): update dependency @angular/core to v20 [security] - autoclosed Jul 20, 2026

renovate Bot closed this Jul 20, 2026

fix(deps): update dependency @angular/core to v20 [security]

28e4088

renovate Bot changed the title ~~fix(deps): update dependency @angular/core to v20 [security] - autoclosed~~ fix(deps): update dependency @angular/core to v20 [security] Jul 20, 2026

renovate Bot reopened this Jul 20, 2026

renovate Bot force-pushed the renovate/npm-angular-core-vulnerability branch 2 times, most recently from 2dd317f to 28e4088 Compare July 20, 2026 07:59

Navigation Menu

fix(deps): update dependency @angular/core to v20 [security] - #125

fix(deps): update dependency @angular/core to v20 [security]#125
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-angular-core-vulnerability

renovate Bot commented Jan 10, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Jan 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Jan 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

@​angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

Details

Impact

Attack Preconditions

Patches

Severity

References

Angular: Template and Attribute Namespace Sanitization Bypass (XSS)

Details

Impact

Attack Preconditions

Patches

Severity

References

Angular i18n vulnerable to Cross-Site Scripting

Details

Impact

Attach Preconditions

Patches

Workarounds

References

Severity

References

Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes

Details

Impact

Patched Versions

Workarounds

Severity

References

Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

Details

Impact

Patched Versions

Workarounds

A. Avoid Dynamic/User-Controlled IDs

B. Configure a Custom Application ID

Severity

References

Release Notes

v20.0.0

Breaking Changes

common

compiler

core

router

Deprecations

core

platform-browser

platform-server

common

compiler

compiler-cli

core

forms

http

platform-browser

Configuration

Uh oh!

renovate Bot commented Jan 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Jan 10, 2026 •

edited

Loading

@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

`v20.0.0`

renovate Bot commented Jan 10, 2026 •

edited

Loading