CVE-2025-31162 | fig2dev float point exception

Exp

Floating point exception in fig2dev in version 3.2.9a allows an attacker to availability via local input manipulation via get_slope function.

Published: 2025-03-28 Last update: 2025-11-03 Assigner: 74b3a70d-cca6-4d34-9789-e83b222ae3be Source: 74b3a70d-cca6-4d34-9789-e83b222ae3be
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31162 is rated Exploit Available (51.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.11%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2025-31162

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

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-01-22 0.01% 0.11% +0.10%
2 2025-03-29 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 4.7 74b3a70d-cca6-4d34-9789-e83b222ae3be

Weakness enumeration for CVE-2025-31162

OS Trackers for CVE-2025-31162

vendor priority summary link
alpine — CVE-2025-31162: 1 source package rows (fig2dev); 4 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 4. https://security.alpinelinux.org/vuln/CVE-2025-31162
debian not yet assigned CVE-2025-31162 not yet assigned priority: Debian including 1 source packages (fig2dev), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-31162
suse medium CVE-2025-31162 severity moderate: SUSE including 3 source package names (transfig-3.2.8b-2.23.1, transfig-3.2.9a-150600.3.5.1, transfig-3.2.9a-2.1), 8 product×package rows across 8 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP6, SUSE Linux Enterprise Module for Package Hub 15 SP7, … (8 product lines)): Fixed 8. https://www.suse.com/security/cve/CVE-2025-31162/
ubuntu medium CVE-2025-31162 medium priority: Ubuntu including 1 source packages (fig2dev), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): released 6, not-affected 2. https://ubuntu.com/security/CVE-2025-31162

Affected software / configurations for CVE-2025-31162

Vendor Product Version Raw CPE
fig2dev_project fig2dev 3.2.9a cpe:2.3:a:fig2dev_project:fig2dev:3.2.9a:*:*:*:*:*:*:*

References for CVE-2025-31162

cvelogic Threat Intelligence