Repository navigation
chore(deps): update dependency @angular/common to v20.3.34 [security] - #2252
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
Size Change: 0 B Total Size: 220 kB ℹ️ View Unchanged
|
More templates
@tanstack/angular-db
@tanstack/browser-db-sqlite-persistence
@tanstack/capacitor-db-sqlite-persistence
@tanstack/cloudflare-durable-objects-db-sqlite-persistence
@tanstack/db
@tanstack/db-ivm
@tanstack/db-sqlite-persistence-core
@tanstack/electric-db-collection
@tanstack/electron-db-sqlite-persistence
@tanstack/expo-db-sqlite-persistence
@tanstack/node-db-sqlite-persistence
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/react-native-db-sqlite-persistence
@tanstack/react-router-with-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/tauri-db-sqlite-persistence
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
20.3.32→20.3.34@angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)
CVE-2026-111753 / GHSA-jfgx-762w-99vr
More information
Details
An incomplete fix for GHSA-58c5-g7wp-6w37 (
CVE-2025-66035) in@angular/common's HTTP Client (HttpClient) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser.Technical Description
To address
CVE-2025-66035,xsrfInterceptorFnintroduced a regular expression (const ABSOLUTE_URL_REGEX = /^(?:https?:)?\/\//i) to detect and skip absolute and protocol-relative URLs before attaching theX-XSRF-TOKENheader.However, browsers resolve request URLs passed to
fetch()andXMLHttpRequest.open()using the WHATWG URL parser. Forhttp:andhttps:schemes, the WHATWG URL standard performs several normalizations prior to resolving the authority/origin:\) are treated as forward slashes (/) — e.g.,/\evil.example/x,\\evil.example/x,\/evil.example/x,https:\\evil.example/x,https:/\evil.example/x.<= 0x20) are stripped — e.g.,' //evil.example/x','\0//evil.example/x','\x1f//evil.example/x'.\t), newline (\n), and carriage return (\r) characters are removed anywhere in the input — e.g.,'/\t/evil.example/x','/\n/evil.example/x','htt\tps://evil.example/x'.Because these URLs do not match
/^(?:https?:)?\/\//i,xsrfInterceptorFntreats them as relative same-origin URLs and attaches theX-XSRF-TOKENheader, while the browser resolves and dispatches the request to the cross-origin host (evil.example).Note: Angular
21.0.3+and22.xreplaced the regular expression with a WHATWGnew URL(req.url, locationOrigin)origin comparison in #65683 and were already unaffected. However, the20.3.xLTS branch retained the regular expression until20.3.34.Impact
The token leakage bypasses Angular's built-in XSRF protection on affected versions, allowing an attacker to capture the user's valid
X-XSRF-TOKENheader if their server permits the request and custom header via CORS. Once obtained, the attacker can perform Cross-Site Request Forgery (CSRF) attacks against the victim user's session.Attack Preconditions
HttpClient).POST,PUT,DELETE,PATCH) to a URL they control (such as/\attacker.example/apior//attacker.example/api).Patches
The issue is resolved by parsing and comparing the request URL's origin against the application's current origin using the standard
URLconstructor (new URL(req.url, locationOrigin)).21.0.3(and all22.xreleases)20.3.34Workarounds
If you cannot immediately upgrade to a patched version:
new URL(url, window.location.origin)and verify thatparsedUrl.origin === window.location.originbefore passing dynamic URLs to mutatingHttpClientrequests.HttpClientmutating methods.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
angular/angular (@angular/common)
v20.3.34Compare Source
core
http
v20.3.33Compare Source
platform-server
router
Configuration
📅 Schedule: (UTC)
🚦 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.