CVE-2026-56355
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2026-56355 is a low-severity Incorrect Behavior Order (CWE-696) vulnerability in Gnu (inferred from references). Its CVSS base score is 3.7 (Low).
Operationally, ranked at the 33th 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 RA-5 (Vulnerability Monitoring and Scanning) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-38135
Vulnerability Data
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages can discover incorrect ordering of related behaviors before deployment.
Vulnerability scanning may surface order-related weaknesses after code is built but does not address their root cause.
Mandating a documented development process and standards enforces review of behavior ordering within the software lifecycle.
Security and privacy engineering principles applied during design and implementation directly require correct sequencing of operations to avoid introducing order-dependent flaws.
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 enforce correct sequencing of security-relevant operations during design and coding.
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 ordering flaws but does not prevent them during development.
Secure development life cycle mandates correct sequencing of security activities, directly preventing incorrect behavior order.
Secure system architecture and engineering principles require proper ordering of design and implementation steps.
Secure coding standards enforce correct execution order of security-critical operations.
Change management may catch order-related issues during reviews but does not address root cause.