CVE-2026-95125

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

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.

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.

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

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.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 14:41 UTCEG score recompute
  4. 2026-10-12 00:57 UTCGHSA enrichmentGHSA-m7q2-jh2f-g569
  5. 2026-10-11 19:11 UTCEG score recompute
  6. 2026-10-11 16:27 UTCEG score recompute
  7. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-11 13:40 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-08 21:38 UTCGHSA enrichmentGHSA-m7q2-jh2f-g569
  12. 2026-10-08 15:19 UTCNVD update
  13. 2026-10-08 14:21 UTCEG score recompute
  14. 2026-10-08 14:16 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-95125?
CVE-2026-95125 is a vulnerability whose severity is not yet rated; its CVE record was published on October 8, 2026. 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.
When was the CVE record for CVE-2026-95125 published?
The CVE record for CVE-2026-95125 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-95125 actively exploited?
CVE-2026-95125 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-95125?
No fix for CVE-2026-95125 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory 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. The vendor advisories EchelonGraph has for CVE-2026-95125 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-95125

Explore →

Is Your Infrastructure Affected by CVE-2026-95125?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.