# CVE-2025-31164: fig2dev heap-buffer overflow

> A heap-buffer overflow in fig2dev allows local attackers to cause a denial of service via crafted input.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-31164, GHSA-p47h-x29h-rvvm, UBUNTU-CVE-2025-31164

## What is CVE-2025-31164?

CVE-2025-31164 is a medium-severity memory corruption vulnerability in xfig fig2dev, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

heap-buffer overflow in fig2dev in version 3.2.9a allows an attacker to availability via local input manipulation via  create_line_with_spline.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-31164?

It affects 1 product.


Products: Fig2dev Project Fig2dev.

## How do I fix CVE-2025-31164?

Upgrade to a fixed version.

## Is CVE-2025-31164 being exploited?

There is no known exploitation of CVE-2025-31164 in the wild and no public exploit code.

## Other vulnerabilities in xfig fig2dev

- [CVE-2025-46397](https://insights.sbomify.com/CVE-2025-46397/): Xfig: xfig: stack-overflow allows possible code execution via local input manipulation (high 7.8)
- [CVE-2025-31162](https://insights.sbomify.com/CVE-2025-31162/): fig2dev float point exception (medium 6.6)
- [CVE-2025-31163](https://insights.sbomify.com/CVE-2025-31163/): fig2dev segmentation fault (medium 6.6)
- [CVE-2025-46398](https://insights.sbomify.com/CVE-2025-46398/): Xfig: fig2dev stack-overflow via read_objects (medium 5.5)
- [CVE-2025-46399](https://insights.sbomify.com/CVE-2025-46399/): Xfig: transfig: fig2dev segmentation fault vulnerability (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31164 and fix it if it is affected.

What it is: CVE-2025-31164 is a medium-severity memory corruption vulnerability in xfig fig2dev, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31164 in the wild and no public exploit code.

Affected product: xfig fig2dev. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31164/ (Markdown: https://insights.sbomify.com/CVE-2025-31164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31164
- OSV: https://osv.dev/vulnerability/CVE-2025-31164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31164/
Summaries are generated and may contain mistakes; the official description above is the record.