Cyber Resilience

CVE-2026-40227

Systemd Project Systemd 260

Published
10 April 2026
Modified
14 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0020 10th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2026-40227 is a medium-severity Comparison Using Wrong Factors (CWE-1025) vulnerability in Systemd Project Systemd. Its CVSS base score is 6.2 (Medium).

Operationally, ranked at the 10th 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-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC API call with an array or map that has a null element.

CWE(s)
CWE-1025

Related Threats

CVEs Like This One

CVE-2026-40228Same product: Systemd Project Systemd
CVE-2026-29111Same product: Systemd Project Systemd
CVE-2023-31438Same product: Systemd Project Systemd
CVE-2023-31439Same product: Systemd Project Systemd
CVE-2023-31437Same product: Systemd Project Systemd
CVE-2026-40224Same product: Systemd Project Systemd
CVE-2026-40225Same product: Systemd Project Systemd
CVE-2023-26604Same product: Systemd Project Systemd
CVE-2023-7008Same product: Systemd Project Systemd
CVE-2025-2888Shared CWE-1025

Affected Assets

systemd project
systemd
260

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incorrect comparison logic after implementation but does not stop the flaw from being written.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and tools can embed standards that reduce introduction of erroneous comparison factors.

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.

PR.PS-06 mostly match
prevents

Secure SDLC activities such as code review and logic testing directly prevent incorrect comparison factors in code.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incorrect comparison results during development and acceptance.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes requirements and reviews that can catch incorrect comparison logic.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct comparison criteria and validation rules.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper comparison logic and factor selection.

References