CVE-2025-31160

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.

Published: 2025-03-26 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31160 is rated Low Risk (16/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.04%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-31160

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-04 0.08% 0.04% -0.04%
2 2025-07-26 0.01% 0.08% +0.07%
3 2025-03-27 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-31160

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.4 1.4 [email protected]

Weakness enumeration for CVE-2025-31160

OS Trackers for CVE-2025-31160

vendor priority summary link
alpine low CVE-2025-31160: 1 source package rows (atop); 7 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 3, open 4. https://security.alpinelinux.org/vuln/CVE-2025-31160
debian not yet assigned CVE-2025-31160 not yet assigned priority: Debian including 1 source packages (atop), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-31160
gentoo high CVE-2025-31160: 1 GLSA(s) (202505-09), 1 atom(s) (sys-process/atop); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-31160
ubuntu medium CVE-2025-31160 medium priority: Ubuntu including 1 source packages (atop), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needed 7, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2025-31160

Affected software / configurations for CVE-2025-31160

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-31160

cvelogic Threat Intelligence