CVE-2026-3587
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2026-3587 is a critical-severity Hidden Functionality (CWE-912) vulnerability in Certvde (inferred from references). Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked at the 49th 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.
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-2026-3587 is a critical vulnerability (CVSS 3.1 score of 10.0; AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) classified under CWE-912 (Hidden Functionality). Published on 2026-03-23, it involves a hidden function within the CLI prompt of an affected device that allows escape from the restricted interface. This flaw enables unauthenticated remote attackers to achieve full compromise of the device.
An unauthenticated remote attacker can exploit this vulnerability over the network with low complexity and no user interaction required. Successful exploitation grants high confidentiality, integrity, and availability impacts, along with a change in scope, culminating in complete device takeover.
For mitigation details, refer to the advisory at https://certvde.com/de/advisories/VDE-2026-020.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14385
Vulnerability Data
An unauthenticated remote attacker can exploit a hidden function in the CLI prompt to escape the restricted interface, leading to full compromise of the device.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
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.
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 and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.