Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HSummary
CVE-2025-12106 is a critical-severity Buffer Over-read (CWE-126) vulnerability in Openvpn Openvpn. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 43th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — 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.
CVE-2025-12106 is a vulnerability caused by insufficient argument validation in OpenVPN versions 2.7_alpha1 through 2.7_rc1. The flaw enables an attacker to trigger a heap buffer over-read during IP address parsing. Published on 2025-12-01, it carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H) and maps to CWE-126 (Buffer Over-read).
The vulnerability can be exploited by a remote, unauthenticated attacker over the network with low complexity and no user interaction required. Exploitation leads to high confidentiality impact, potentially allowing sensitive data exposure from heap memory, and high availability impact, such as server crashes or denial of service.
Mitigation details are provided in advisories from the OpenVPN community at https://community.openvpn.net/Security%20Announcements/CVE-2025-12106 and the mailing list announcement at https://www.mail-archive.com/openvpn-announce@lists.sourceforge.net/msg00152.html.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-199988
Vulnerability Data
Insufficient argument validation in OpenVPN 2.7_alpha1 through 2.7_rc1 allows an attacker to trigger a heap buffer over-read when parsing IP addresses
- 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 (static analysis, fuzzing, bounds checking tests) directly finds buffer over-read flaws.
Engineering principles such as memory-safe design and bounds-checked abstractions structurally stop introduction of out-of-bounds reads.
Process isolation limits the blast radius of an over-read to the compromised domain.
Input validation enforces length and index constraints that prevent many externally triggered over-reads.
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 development practices directly prevent introduction of buffer over-read weaknesses.
Vulnerability identification processes can discover buffer over-read flaws via scanning or review.
Patching or replacing vulnerable software removes known instances of buffer over-read bugs.
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 in development can detect buffer over-reads before release.
Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.
Application security requirements can specify buffer-size and bounds-checking rules.
Secure architecture principles include memory-safety and bounds-checking design choices.
Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.