CVE-2026-95116

waiting for further signalsZero needs more public information before it can validate it.

GHSA-w3m4-q296-772h ↗EUVD-2026-95303 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
libming n/a
ETK-2026-1996Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 01h 33msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+258h16m
0
+2h
+4h
+6h
+8h
+10h

description

libming through version 0.4.8 is affected by a resource-exhaustion flaw while reading SWF content. A remote attacker may disrupt availability when an application accepts and processes attacker-controlled files through the affected parsing path.

mitigation

Do not process untrusted SWF input with affected libming deployments; restrict access to upload or conversion endpoints that invoke the parser. Run necessary processing with resource limits and isolation until a vendor-confirmed updated release is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.39%31st percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 00:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-08 00:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-08 00:00Z

this entry in the feed

GET /api/v1/feed/CVE-2026-95116

{
  "etk_id": "ETK-2026-1996",
  "cve_id": "CVE-2026-95116",
  "display_id": "CVE-2026-95116",
  "ghsa_id": "GHSA-w3m4-q296-772h",
  "euvd_id": "EUVD-2026-95303",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Remote denial of service in libming SWF parsing",
  "summary": "libming through version 0.4.8 is affected by a resource-exhaustion flaw while reading SWF content. A remote attacker may disrupt availability when an application accepts and processes attacker-controlled files through the affected parsing path.",
  "mitigation": "Do not process untrusted SWF input with affected libming deployments; restrict access to upload or conversion endpoints that invoke the parser. Run necessary processing with resource limits and isolation until a vendor-confirmed updated release is available.",
  "vendor": null,
  "product": "libming",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0039,
  "epss_percentile": 0.3126,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.641492466666666,
  "t0_at": "2026-10-08T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T00:00:00+00:00",
      "url": "https://github.com/advisories/GHSA-w3m4-q296-772h"
    }
  }
}

published 2026-10-18 17:55Z
last change 2026-10-21 18:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.