Security Resilience

CVE-2025-30185

Published
11 November 2025
Modified
19 October 2026
CVSS Score v4 8.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/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.0013 3th percentile
Risk Priority 25 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-30185 is a high-severity Active Debug Code (CWE-489) vulnerability in Intel UEFI (inferred from references). Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked at the 3th 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 CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Active debug code for some Intel UEFI reference platforms within Ring 0: Kernel may allow a denial of service and escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable data alteration.…

more

This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (high) impacts.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1137.002 Office Test Persistence
Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1599 Network Boundary Bridging Defense Impairment
Adversaries may bridge network boundaries by compromising perimeter network devices or internal devices responsible for network segmentation.
T1686.002 Network Device Firewall Defense Impairment
Adversaries may disable network device-based firewall mechanisms entirely or add, delete, or modify particular rules in order to bypass controls limiting network usage.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21785Shared CWE-489
CVE-2024-29075Shared CWE-489
CVE-2026-58378Shared CWE-489
CVE-2026-66403Shared CWE-489
CVE-2025-15017Shared CWE-489
CVE-2026-81943Shared CWE-489
CVE-2023-21496Shared CWE-489
CVE-2025-64983Shared CWE-489
CVE-2023-4804Shared CWE-489
CVE-2026-66405Shared CWE-489

Affected Assets

Intel
UEFI
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Baseline configuration defines the approved production state that must exclude active debug code.

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

Documented development standards and tools can require removal of debug code before release.

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

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
blocks

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

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.

finds

Security testing in development and acceptance catches active debug code before deployment.

blocks

Configuration management can disable or remove debug features through hardened baselines.

prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

blocks

Change management can enforce removal of debug code as part of release gates.

References