BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2025-66035High confidence

Angular HTTP Client Has XSRF Token Leakage via Protocol-Relative URLs

angular · angular

7.7HighCVSS 4.0

Recommended action

Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`angular.js`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current

SSA-253495 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

RUGGEDCOM RST2428P (6GK6242-6PA00)

Summary: Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding 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.
Remediation: Update to V4.0 or later version

SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIDIS Prime

Summary: Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding 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.
Remediation: Update to V4.0.800 or later version

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2025-199769

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding 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.

What

Why

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Insertion of Sensitive Information Into Sent Data → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Not a CVSS 4.0 base metric
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-201 ↗
CWE-201: Insertion of Sensitive Information Into Sent Data. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical 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:N
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land: Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.

NetworkUnauthenticatedCWE-201

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-199769Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2026-0778Dell Secure Connect Gateway Policy Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway Policy Manager ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory

BSI · German · WID-SEC-W-2025-2689Angular: Schwachstelle ermöglicht Offenlegung von Informationen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Angular ausnutzen, um Informationen offenzulegen.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0698Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-13465 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2025-66031 Référence CVE CVE-2025-66035 https://www.cve.org/CVERecord?id=CVE-2025-66035 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-1525 https://www.cve.org/CVERecord?id=CVE-2026-1525 Référence CVE CVE-2026-1526 https://www.cve.org/CVERecord?id=CVE-2026-1526 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-1528 https://www.cve.org/CVERecord?id=CVE-2026-1528 Référence CVE CVE-2026-22007 https://www.cve.org/CVERecord?id=CVE-2026-22007 Référence CVE CVE-2026-22013 https://www.cve.org/CVERecord?id=CVE-2026-2

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0523Multiples vulnérabilités dans les produits IBM

IBM 7270868 du 27 avril 2026 https://www.ibm.com/support/pages/node/7270868 Bulletin de sécurité IBM 7270869 du 27 avril 2026 https://www.ibm.com/support/pages/node/7270869 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2024-31033 https://www.cve.org/CVERecord?id=CVE-2024-31033 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-66035 https://www.cve.org/CVERecord?id=CVE-2025-66035 Référence CVE CVE-2025-66412 https://www.cve.org/CVERecord?id=CVE-2025-66412 Référence CVE CVE-2025-67030 https://www.cve.org/CVERecord?id=CVE-2025-67030 Référence CVE CVE-2025-68470 https://www.cve.org/CVERecord?id=CVE-2025-68470 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-22029 https://www.cve.org/CVERecord?id=CVE-2026-22029 Référence CVE CVE-2026-22610 https://www.cve.org/CVERecord?id=CVE-2026-22610 Référence CVE CVE-2026-22735 https://www.cve.org/CVERecord?id=CVE-2026-22735 Référence CVE CVE-2026-22737 https://www.cve.org/CVERecord?id=CV

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0224Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-40240 Référence CVE CVE-2025-40248 https://www.cve.org/CVERecord?id=CVE-2025-40248 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-61140 https://www.cve.org/CVERecord?id=CVE-2025-61140 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-65106 https://www.cve.org/CVERecord?id=CVE-2025-65106 Référence CVE CVE-2025-66019 https://www.cve.org/CVERecord?id=CVE-2025-66019 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2025-66031 Référence CVE CVE-2025-66035 https://www.cve.org/CVERecord?id=CVE-2025-66035 Référence CVE CVE-2025-66221 https://www.cve.org/CVERecord?id=CVE-2025-66221 Référence CVE CVE-2025-66412 https://www.cve.org/CVERecord?id=CVE-2025-66412 Référence CVE CVE-2025-66418 https://www.cve.org/CVERecord?id=CVE-2025-66418 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-68146 https://www.cve.org/CVERecord?id=CVE-2025-68146 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68480 https://www.cve.org/CVERecord?id=CVE-2025-68480 Référence CVE CVE-2025-68615 https://www.cve.org/CVERecord?id=

Official advisory

NCSC-NL · Dutch · NCSC-2026-0079Kwetsbaarheden verholpen in Siemens producten

The document outlines a vulnerability in Angular's HttpClient that allows unauthorized disclosure of the XSRF token due to improper handling of protocol-relative URLs, affecting versions prior to 19.2.16, 20.3.14, and 21.0.1.

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: RUGGEDCOM RST2428P (6GK6242-6PA00)
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: Update to V4.0 or later version
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 26 Nov 2025 · Last source change 2 Jun 2026, 13:00 UTC · CWE-201 · Insertion of Sensitive Information Into Sent Data

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2025-199769

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

CWE sourceCNA

NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-11-26CVE published

ENISA EUVD · EUVD-2025-199769↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Angular HTTP Client Has XSRF Token Leakage via Protocol-Relative URLs

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2025-199769

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.