libming v0.4.8 was discovered to contain a memory leak via the parseSWF_PLACEOBJECT3 function.

published 2025-03-27 last yr. modified 2026-06-17 4mo ago also EUVD-2025-8451

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits: 0; none known

Is CVE-2025-29486 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: last yr. (2025-03-28)

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/libming/libming/issues/330 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/goodmow/PoC/blob/main/libming/libming-fuzz3.readme referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

github.com /libming/libming/issues/330
exploit, issue-tracking, vendor-advisory
github.com /goodmow/PoC/blob/main/libming/libming-fuzz3.readme
exploit

Sources

CVE List CVE-2025-29486
NVD CVE-2025-29486

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.