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

renovate · 2025-11-27T06:33:58Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client

CVE-2025-66035 / GHSA-58c5-g7wp-6w37

More information

Details

The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain.

Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header.

Impact

The token leakage completely bypasses Angular's built-in CSRF protection, allowing an attacker to capture the user's valid XSRF token. Once the token is obtained, the attacker can perform arbitrary Cross-Site Request Forgery (CSRF) attacks against the victim user's session.

Attack Preconditions

The victim's Angular application must have XSRF protection enabled.
The attacker must be able to make the application send a state-changing HTTP request (e.g., POST) to a protocol-relative URL (e.g., //attacker.com) that they control.

Patches

19.2.16
20.3.14
21.0.1

Workarounds

Developers should avoid using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Severity

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

References

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

@angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

CVE-2026-50171 / GHSA-p3vc-36g9-x9gr

More information

Details

A Denial of Service (DoS) vulnerability exists in the @angular/common package of Angular. The formatNumber function, which is also utilized by DecimalPipe, PercentPipe, and CurrencyPipe, does not properly validate the upper bounds of the digitsInfo parameter. Specifically, the minimum and maximum fraction digits parsed from the digitsInfo string (e.g., 1.2-4) are converted to integers and used without limits.

When parsing a maliciously crafted digitsInfo string with excessively large fraction digit values (e.g., 1.200000000-200000000), the internal roundNumber function attempts to pad the digits array to match the requested fraction size. This results in an unbounded loop that repeatedly pushes elements into an array.

Impact

Successful exploitation of this vulnerability allows an attacker to trigger resource exhaustion, leading to a Denial of Service (DoS):

Server-Side Rendering (SSR): In applications using SSR (e.g., @angular/ssr), an attacker can crash the Node.js server process due to a JavaScript heap out of memory error. This affects the availability of the application for all users.
Client-Side Rendering (CSR): In standard client-side applications, the unbounded loop will block the main thread, freezing the user's browser tab and making it unresponsive.

Attack Preconditions

For this vulnerability to be exploitable, the following conditions must be met:

Vulnerable Component Usage: The application must use Angular's number formatting utilities, such as the formatNumber function directly, or via template pipes (DecimalPipe, PercentPipe, CurrencyPipe).
Attacker-Controlled Parameter: The digitsInfo parameter passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preference settings, or API responses that accept user-defined formatting options). If digitsInfo is trusted or limited to a known, defined range for its value, the vulnerability is not exploitable by external attackers.

Patches

22.0.0-rc.2
21.2.15
20.3.22
19.2.23

Credits

This vulnerability was discovered and reported by CodeMender from Google DeepMind.

Severity

CVSS Score: 8.2 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/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/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

CVE-2026-50170 / GHSA-q6f4-qqrg-jv6x

More information

Details

A vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState.

However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared TransferState payload. When these responses are serialized into the HTML, any caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability.

Impact

Successful exploitation allows an unauthenticated attacker to obtain sensitive, user-specific information of other authenticated users. This occurs when:

The SSR-rendered HTML containing the cached private data is stored in a shared cache (e.g., CDN, reverse proxy).
Subsequent requests for the same page receive the cached HTML containing the first user's private data.

Attack Preconditions

SSR and Hydration Enabled: The Angular application must be configured to use Server-Side Rendering and hydration (e.g., using provideClientHydration()).
Credentialed Requests during SSR: The application must perform HTTP requests that require user-specific authentication (using cookies or withCredentials: true) during the initial server-side render.
Shared Caching: The application's HTML responses must be cached by a shared caching layer (CDN, reverse proxy, or server-side cache) without proper cache-control headers to distinguish authenticated users.

Patches

22.0.0-rc.2
21.2.15
20.3.22
19.2.23

Severity

CVSS Score: 8.2 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/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/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning

CVE-2026-54266 / GHSA-39pv-4j6c-2g6v

More information

Details

Angular's HttpTransferCache caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in TransferState using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters).

The cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions.

An attacker can easily find a query parameter string (e.g., q=aaCAZMMM for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., /api/user/profile). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the TransferState cache.

Impact

When the application attempts to retrieve the cached response for the sensitive endpoint (such as the user's profile), it receives the attacker-controlled response instead. This results in:

State Poisoning: The application runs with attacker-forged data, which can lead to bypassing client-side security controls or DOM-based Cross-Site Scripting (XSS) if the data is rendered unsafely.
Information Leakage: If the sensitive response is mistakenly associated with the attacker's search results and rendered on the page, the victim's sensitive data may be disclosed to the attacker.

Patched Versions

22.0.1
21.2.17
20.3.25

Framework-Level Fix

The logic has been updated to use a cryptographically secure SHA-256 hash algorithm for generating TransferState cache keys in HttpTransferCache. The cache keys are now 256-bit hexadecimal strings.

Workarounds

If you cannot upgrade immediately, configure your HttpClient requests to skip transfer caching for sensitive endpoints:

this.http.get('/api/user/profile', {
  transferCache: false
});

Alternatively, disable the HTTP transfer cache globally in your application bootstrap config:

import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';

export const appConfig = {
  providers: [
    provideClientHydration(
      withNoHttpTransferCache()
    )
  ]
};

Credits

This vulnerability was discovered and reported by CodeMender from Google DeepMind.

Severity

CVSS Score: 8.8 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)

CVE-2026-54268 / GHSA-48r7-hpm6-gfxm

More information

Details

A Denial of Service (DoS) vulnerability exists in the @angular/common package of the Angular framework. The formatDate function, which is also utilized by the standard Angular DatePipe, does not properly limit or validate the length of the format parameter.

When parsing a maliciously crafted, excessively long date format string (e.g., a repeating pattern or very large string), the internal parser splits the string iteratively using a regular expression loop. This results in uncontrolled resource consumption (high CPU utilization and excessive memory allocations), leading to a Denial of Service (DoS).

Impact

1. Server-Side Rendering (SSR)

In Angular applications that leverage Server-Side Rendering, an attacker can supply a malicious payload with an excessively long date format string. Processing this on the server causes high CPU usage and triggers a JavaScript heap out of memory crash, rendering the application unavailable to all users.

2. Client-Side Rendering (CSR)

In standard client-side applications, executing the vulnerable function with an excessively long format string blocks the browser's main thread, causing the browser tab to freeze and become completely unresponsive.

Patched Versions

22.0.1
21.2.17
20.3.25

Attack Preconditions

For this vulnerability to be exploitable, both of the following conditions must be met:

Vulnerable Component Usage: The application must format dates using the formatDate utility or the DatePipe.
Attacker-Controlled Parameter: The date format string passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preferences, or API responses).

If the date format is hardcoded (e.g., 'mediumDate', 'shortTime', or static strings) or properly validated to be within a reasonable length limit, the application is not vulnerable.

Severity

CVSS Score: 8.2 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/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: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning

CVE-2026-68945 / GHSA-jhpw-976m-542j

More information

Details

Angular's HttpTransferCache caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration.

During SSR, HttpTransferCache previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas:

new HttpParams().set('role', 'user,admin')
new HttpParams().append('role', 'user').append('role', 'admin')

Both requests previously serialized as role=user,admin, allowing distinct HttpClient requests to produce the same transfer-cache key material.

Impact

In an SSR application, this cache-key ambiguity can make a later security-sensitive HttpClient request receive the response from an earlier semantically different request in the same render. For example, an attacker-influenced scalar-comma request can be cached and then replayed as the response for a trusted repeated-param authorization or data request to the same URL. As a result, Angular's server-rendered output can be based on the wrong backend response because the trusted request is not dispatched. This can lead to:

State Poisoning: Using incorrect or attacker-influenced cached responses for subsequent application logic.
Cross-Request Response Reuse: Reusing cached responses across requests with semantically different parameters.

Patched Versions

22.0.2
21.2.19
20.3.27

Workarounds

If you cannot upgrade immediately, configure your HttpClient requests to skip transfer caching for sensitive endpoints where repeated parameter keys are used:

this.http.get('/api/resource', {
  transferCache: false
});

Alternatively, disable the HTTP transfer cache globally in your application bootstrap config:

import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';

export const appConfig = {
  providers: [
    provideClientHydration(
      withNoHttpTransferCache()
    )
  ]
};

Severity

CVSS Score: 8.8 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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).

Release Notes

angular/angular (@angular/common)

`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](https://redirect.github.com/angular/an

✂ 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 · 2025-11-27T06:34:00Z

⚠️ 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 unable to resolve dependency tree
npm error
npm error While resolving: graph-flow@0.6.4
npm error Found: @angular/core@16.2.12
npm error node_modules/@angular/core
npm error   @angular/core@"^16.2.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"20.3.27" from @angular/common@20.3.27
npm error node_modules/@angular/common
npm error   @angular/common@"^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_12_880Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-30T20_41_12_880Z-debug-0.log

renovate Bot added dependencies renovate security labels Nov 27, 2025

renovate Bot added renovate security labels Nov 27, 2025

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

renovate Bot closed this Mar 29, 2026

renovate Bot deleted the renovate/npm-angular-common-vulnerability branch March 29, 2026 04:53

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

renovate Bot reopened this Mar 29, 2026

renovate Bot force-pushed the renovate/npm-angular-common-vulnerability branch 2 times, most recently from b8813e1 to c037074 Compare March 29, 2026 08:42

renovate Bot force-pushed the renovate/npm-angular-common-vulnerability branch from c037074 to 4ddf486 Compare July 16, 2026 00:39

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

renovate Bot force-pushed the renovate/npm-angular-common-vulnerability branch from 4ddf486 to 3e64453 Compare July 20, 2026 03:32

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

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

985368b

renovate Bot force-pushed the renovate/npm-angular-common-vulnerability branch from 3e64453 to 985368b Compare July 20, 2026 07:58

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

Navigation Menu

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

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

renovate Bot commented Nov 27, 2025 •

edited

Loading

Uh oh!

renovate Bot commented Nov 27, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client

Details

Impact

Attack Preconditions

Patches

Workarounds

Severity

References

@​angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

Details

Impact

Attack Preconditions

Patches

Credits

Severity

References

@​angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

Details

Impact

Attack Preconditions

Patches

Severity

References

@​angular/common: Weak 32-Bit Cache Key Hashing in HttpTransferCache Leading to Cross-Request Data Leakage and State Poisoning

Details

Impact

Patched Versions

Framework-Level Fix

Workarounds

Credits

Severity

References

@​angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)

Details

Impact

1. Server-Side Rendering (SSR)

2. Client-Side Rendering (CSR)

Patched Versions

Attack Preconditions

Severity

References

Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning

Details

Impact

Patched Versions

Workarounds

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

Configuration

Uh oh!

renovate Bot commented Nov 27, 2025 • 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

renovate Bot commented Nov 27, 2025 •

edited

Loading

@angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

@angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning

@angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)

`v20.0.0`

renovate Bot commented Nov 27, 2025 •

edited

Loading