Security Resilience

CVE-2025-31160

Published
26 March 2025
Modified
15 April 2026
CVSS Score v3.1 2.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0022 12th percentile
Risk Priority 26 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-31160 is a low-severity Reachable Assertion (CWE-617) vulnerability in Ycombinator (inferred from references). Its CVSS base score is 2.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Defense Impairment (T1687); ranked at the 12th 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.

EU & UK References

Vulnerability Data

atop through 2.11.0 allows local users to cause a denial of service (e.g., assertion failure and application exit) or possibly have unspecified other impact by running certain types of unprivileged processes while a different user runs atop.

CWE(s)
CWE-617

Related Threats

MITRE ATT&CK Enterprise Techniques

T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37002Shared CWE-617
CVE-2023-38469Shared CWE-617
CVE-2026-82065Shared CWE-617
CVE-2026-101984Shared CWE-617
CVE-2026-25610Shared CWE-617
CVE-2023-34194Shared CWE-617
CVE-2026-102063Shared CWE-617
CVE-2025-48023Shared CWE-617
CVE-2026-13073Shared CWE-617
CVE-2025-40777Shared CWE-617

Affected Assets

Ycombinator
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation finds reachable assertions during development.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles discourage use of assertions for handling untrusted input.

SI-10 Information Input Validation partial match

Validating untrusted inputs structurally prevents attacker data from reaching and triggering assertions.

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
blocks

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
blocks

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

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 in development can detect reachable assertions before release, reducing the likelihood of exploitation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

References