Cyber Resilience

CVE-2025-66035

Info Disclosure

Info Disclosure
Published
26 November 2025
Modified
02 June 2026
CVSS Score v4 7.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0065 48th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-66035 is a high-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Siemens (inferred from references). Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-21 (Information Sharing) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-201CWE-359

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1025 Data from Removable Media Collection
Adversaries may search connected removable media on computers they have compromised to find files of interest.
attack.mitre.org →
T1039 Data from Network Shared Drive Collection
Adversaries may search network shares on computers they have compromised to find files of interest.
attack.mitre.org →
T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
attack.mitre.org →
T1114 Email Collection Collection
Adversaries may target user email to collect sensitive information.
attack.mitre.org →
T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34226Shared CWE-201, CWE-359
CVE-2024-38103Shared CWE-359
CVE-2025-14317Shared CWE-359
CVE-2026-25699Shared CWE-359
CVE-2025-43496Shared CWE-359
CVE-2025-0679Shared CWE-359
CVE-2024-49025Shared CWE-359
CVE-2025-10859Shared CWE-359
CVE-2023-5983Shared CWE-359
CVE-2024-10267Shared CWE-359

Affected Assets

Siemens
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3
  • V10.3.5
  • V10.7.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces authorizations so that PII is not reachable by unauthorized actors.

AC-4 Information Flow Enforcement good match

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

AC-21 Information Sharing good match

Requires explicit verification that a recipient's authorizations match the sensitivity of shared PII.

AC-6 Least Privilege good match

Limits granted rights to the minimum needed, reducing the set of actors who can reach private data.

PT-2 Authority to Process Personally Identifiable Information good match

Documents the legal or consent basis required before any processing of PII occurs.

PT-4 Consent good match

Implements consent mechanisms that directly block access absent the individual's permission.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

RC.CO-04 partial match
degrades

CWE-359 does not impair RC.CO-04's ability to issue approved public recovery updates, yet any resulting PII exposure can partially undermine the outcome's overall efficacy and trust.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.11 Data masking mostly match
prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

A.8.12 Data leakage prevention mostly match
prevents

Monitoring and quarantining outbound messages that contain personal or private data directly reduces the chance that such information will be disclosed to unauthorized recipients.

A.8.33 Test information mostly match
prevents

The explicit prohibition on copying personally identifiable information into development and test environments directly lowers the exposure of private personal data to staff or processes that should not see it.

A.5.12 Classification of information partial match
mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

A.5.13 Labelling of information partial match
mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

A.5.14 Information transfer partial match
mitigates

Information-transfer rules directly govern what data may be sent to external parties.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Ubuntu 22.04 (1 rule)
  • V-260531 Ubuntu 22.04 LTS must configure the SSH daemon to use FIPS 140-3-approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. prevents CWE-359
Ubuntu 24.04 (1 rule)
  • V-270670 Ubuntu 24.04 LTS must configure the SSH client to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. prevents CWE-359

References