Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2026-41285 is a medium-severity Improper Validation of Specified Quantity in Input (CWE-1284) vulnerability in Openbsd Openbsd. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 11th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23996
Vulnerability Data
In OpenBSD through 7.8, the slaacd and rad daemons have an infinite loop when they receive a crafted ICMPv6 Neighbor Discovery (ND) option (over a local network) with length zero, because of an "nd_opt_len * 8 - 2" expression with…
more
no preceding check for whether nd_opt_len is zero.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.7.2V1.4.2V2.1.1V2.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.
SI-10 requires validity checks on information inputs, directly stopping acceptance of malformed quantities before they can be used.
Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.
Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.
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 can detect missing quantity validation but does not itself implement the control.
Secure development lifecycle mandates input validation for quantity fields, directly preventing CWE-1284.
Application security requirements explicitly call for validation of size/length inputs, mitigating CWE-1284.
Secure architecture principles encourage robust input handling but do not specifically address quantity validation.
Secure coding standards require explicit checks on numeric quantity inputs, fully addressing CWE-1284.
Change management can require review of loop logic when code is modified.