Security readout for executives and security teams
Plain-English summary
Some Angular apps can accidentally send their anti-CSRF token to an external domain when code uses a URL beginning with //. If that domain is attacker controlled, the token may be disclosed. The issue is patched in Angular 19.2.16, 20.3.14, and 21.0.1.
Executive priority
Treat this as a high-priority frontend dependency update where Angular apps handle authenticated sessions. Prioritize externally exposed applications and products using Angular HttpClient with XSRF protection.
Technical view
Angular HttpClient misclassified protocol-relative URLs as same-origin because its cross-origin check looked for http:// or https://. It then attached the X-XSRF-TOKEN header. CVSS 4.0 is 7.7 high; CWE mappings are CWE-201 and CWE-359.
Likely exposure
Exposure is most likely in Angular applications on affected versions that use HttpClient XSRF protection and make requests to URLs beginning with //. Risk increases when those URLs can point to untrusted or attacker-controlled domains.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The disclosed impact is unauthorized XSRF token disclosure through application request logic, not direct server compromise.
Researcher notes
The key condition is use of protocol-relative URLs with Angular HttpClient on affected versions. Evidence supports token leakage; it does not establish broader account takeover or active exploitation. Siemens advisories indicate downstream vendor awareness, but affected product details are not in the bundle.
Mitigation direction
- Upgrade Angular to 19.2.16, 20.3.14, 21.0.1, or later as applicable.
- Avoid protocol-relative URLs in Angular HttpClient requests.
- Use single-slash relative paths for same-origin backend communication.
- Use fully qualified trusted absolute URLs for approved external services.
- Check vendor advisories for downstream product-specific guidance.
Validation and detection
- Inventory Angular package versions across web applications.
- Search HttpClient usage for URLs beginning with //.
- Review runtime configuration that may construct protocol-relative backend URLs.
- Confirm patched Angular versions in lockfiles and deployed builds.
- Check logs or proxies for X-XSRF-TOKEN headers sent to external domains.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-359: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-66035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.7HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516fCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bcCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41eCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/angular/angular/releases/tag/19.2.16CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/angular/angular/releases/tag/20.3.14CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/angular/angular/releases/tag/21.0.1CVE reference, GitHub_M · x_refsource_MISC
- https://cert-portal.siemens.com/productcert/html/ssa-485750.htmlCVE reference, siemens-SADP
- https://cert-portal.siemens.com/productcert/html/ssa-253495.htmlCVE reference, siemens-SADP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposure of Private Personal Information to an Unauthorized Actor
Exposure of Private Personal Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.