libming through 0.4.8 contains a heap buffer overflow in r_readc() in src/blocks/fromswf.c. A crafted SWF file with a malformed or truncated RECT header can cause a denial of service.
CVE-2026-95125
- No CVSS published and no exploitation signals yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "libming through 0.4.8 contains a heap buffer overflow in r_readc() in src/blocks/fromswf.c." No release containing a fix is confirmed on record.
- CVSS v3
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0.2%
- EPSS %ILE
- 5th
- KEV
- Not listed
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 8, 2026
Last Modified
October 8, 2026
References (3)
Vendor Advisories for CVE-2026-95125(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-12 14:41 UTCEG score recompute
- 2026-10-12 00:57 UTCGHSA enrichmentGHSA-m7q2-jh2f-g569
- 2026-10-11 19:11 UTCEG score recompute
- 2026-10-11 16:27 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-11 13:40 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-08 21:38 UTCGHSA enrichmentGHSA-m7q2-jh2f-g569
- 2026-10-08 15:19 UTCNVD update
- 2026-10-08 14:21 UTCEG score recompute
- 2026-10-08 14:16 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-95125?
When was the CVE record for CVE-2026-95125 published?
Is CVE-2026-95125 actively exploited?
How do I remediate CVE-2026-95125?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-95125
Is Your Infrastructure Affected by CVE-2026-95125?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.