chore(deps): update dependency @angular/common [security]#15
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @angular/common [security]#15renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
December 4, 2025 22:35
23b303f to
758bcdb
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
January 8, 2026 23:49
758bcdb to
fe7ac90
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
2 times, most recently
from
March 14, 2026 05:55
6551f2b to
0ed3acd
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
April 15, 2026 19:24
0ed3acd to
b7a03c9
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
April 19, 2026 07:22
b7a03c9 to
3e4630a
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
May 2, 2026 23:23
3e4630a to
0e5710d
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
May 23, 2026 10:52
0e5710d to
154a54e
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
May 24, 2026 15:11
154a54e to
15f4c51
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
May 30, 2026 15:42
15f4c51 to
c6e7eaf
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
2 times, most recently
from
June 7, 2026 19:56
4fc58f6 to
da96dca
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
June 13, 2026 08:03
da96dca to
fdec7f5
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
June 14, 2026 19:54
fdec7f5 to
5aa83a2
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
June 21, 2026 03:30
5aa83a2 to
43e6771
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
June 25, 2026 04:01
43e6771 to
9c6d8e4
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-common-vulnerability
branch
from
July 18, 2026 07:09
9c6d8e4 to
40deca0
Compare
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:
^9.1.12→^9.1.12 || ^22.0.0~9.1.12→~19.2.0Angular 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://orhttps://) 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 theX-XSRF-TOKENheader.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
POST) to a protocol-relative URL (e.g.,//attacker.com) that they control.Patches
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
angular/angular (@angular/common)
v22.0.7Compare Source
common
compiler
compiler-cli
core
forms
http
localize
platform-browser
v22.0.6Compare Source
compiler
compiler-cli
forms/signals
migrations
router
v22.0.5Compare Source
common
compiler-cli
core
router
v22.0.4Compare Source
migrations
v22.0.3Compare Source
compiler
compiler-cli
core
http
service-worker
upgrade
v22.0.2Compare Source
common
compiler
core
http
migrations
v22.0.1Compare Source
Deprecations
platform-server
@angular/platform-serveris deprecated. Use standardfetchAPIs instead.(cherry picked from commit
8446e46)common
compiler
href/xlink:hrefattributes of any element of the MathML namespacecompiler-cli
core
forms
tickadditionalProperties: falseon generated WebMCP formhttp
reportUploadProgressandreportDownloadProgresson post/patch requestslanguage-service
platform-server
router
service-worker
v22.0.0Compare Source
Blog post "Announcing Angular v22".
Breaking Changes
compiler
nullishCoalescingNotNullableandoptionalChainNotNullablediagnostics on exisiting projects.You might want to disable those 2 diagnotiscs in your
tsconfigtemporarily.invariables will throw in template expressions.compiler-cli
core
anyanymore. Make sure the element you pass is not nullable.changeDetectionproperty are nowOnPushby default. SpecifychangeDetection: ChangeDetectionStrategy.Eagerto keep the previous behavior.ChangeDetectorRef.checkNoChangeswas removed. In tests usefixture.detectChanges()instead.createNgModuleRefwas removed, usecreateNgModuleinsteadComponentFactoryResolverandComponentFactoryare no longer available. Pass the component class directly to APIs that previously required a factory, such asViewContainerRef.createComponentor use the standalonecreateComponentFunction.ComponentFactoryResolverandComponentFactoryare no longer available. Pass the component class directly to APIs that previously required a factory, such asViewContainerRef.createComponentor use the standalonecreateComponentfunction.forms
minandmaxvalidation rules no longer supportstring values. Bound values must be numbers or null.
http
HttpXhrBackendwithprovideHttpClient(withXhr)if you want to keep supporting upload progress reports.platform-browser
host. However other DOM on the page may still be affected by those styles if not leveragingViewEncapsulation.Emulatedor if those styles are used by elements outside of Angular, potentially causing other DOM to appear unstyled.router
The return type for
TitleStrategy.getResolvedTitleForRoutewas previously 'any' while the actual return type could only be either
stringor
undefined. The return type now reflects the possible values correctly.Code that reads the value may need to be adjusted.
(cherry picked from commit
ad37f52)The
currentSnapshotparameter inCanMatchFnand thecanMatchmethod of theCanMatchinterface is now required. While this was already the behavior of the Router at runtime, existing class implementations ofCanMatchmust now include the third argument to satisfy the interface.paramsInheritanceStrategy now defaults to 'always'
The default value of paramsInheritanceStrategy has been changed from 'emptyOnly' to 'always'. This means that route parameters are inherited from all parent routes by default. To restore the previous behavior, set paramsInheritanceStrategy to 'emptyOnly' in your router configuration.
provideRoutes()has been removed. UseprovideRouter()orROUTESas multi token if necessary.upgrade
getAngularLib/setAngularLibhave been removed usegetAngularJSGlobal/setAngularJSGlobalinstead.Deprecations
http
withFetchis now deprecated, it can be safely removed.reportProgressoption is deprecated please usereportUploadProgress&reportDownloadProgressinstead.compiler
undefineddata-attributescompiler-cli
core
IdleRequestOptionssupport toIdleServiceprovideWebMcpToolsinjectAsynchelper functionprovideHttpClientto keep using theHttpXhrBackendimplementation.ChangeDetectionStrategy.Eagerwhere applicableApplicationRefwith configdeclareWebMcpToolsupport@ServicedecoratorConfiguration
📅 Schedule: (in timezone Europe/Zurich)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.