CVE-2024-26254
Microsoft Windows 10 1809 ≤ 10.0.17763.5696
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-26254 is a high-severity Untrusted Pointer Dereference (CWE-822) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 13% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft Virtual Machine Bus (VMBus) is affected by a denial-of-service vulnerability tracked as CVE-2024-26254. The flaw carries a CVSS 3.1 score of 7.5 and is associated with CWE-822, allowing an unauthenticated network attacker to disrupt availability without any user interaction or privileges.
An attacker with network access can send crafted traffic to the VMBus component and trigger a denial-of-service condition that impacts the confidentiality or integrity of no data but renders the affected service unavailable. The attack requires no authentication and can be performed remotely over the network.
Microsoft has published guidance for the issue at the MSRC update guide, indicating that patches or configuration changes are available to address the vulnerability. The associated EPSS score has remained flat at 0.0653 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-23530
Vulnerability Data
Microsoft Virtual Machine Bus (VMBus) Denial of Service Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover instances where untrusted data is turned into a pointer and dereferenced.
Validating all information inputs stops untrusted values from being accepted and converted into dereferenceable pointers.
Memory-protection mechanisms limit the damage from an invalid pointer dereference without stopping the root coding flaw.
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.
Secure SDLC practices directly prevent introduction of untrusted pointer handling during development.
Runtime monitoring of software and data can detect adverse events resulting from exploitation of the weakness.
Vulnerability identification processes can discover instances of this weakness via code review or scanning.
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.
Security testing can detect pointer-dereference flaws before release.
Secure development lifecycle includes pointer-safety practices that reduce untrusted pointer dereference risk.
Application security requirements can mandate validation of pointers obtained from untrusted sources.
Secure architecture principles discourage direct use of untrusted values as pointers.
Secure coding standards explicitly forbid dereferencing pointers derived from untrusted input.