CVE-2026-116738

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

GHSA-rhj9-fcgr-5r62 ↗EUVD-2026-110486 ↗

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.
kisli vmime <= 0.9.2
ETK-2026-2710Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 50msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h18m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

VMime through 0.9.2 is affected when it processes malformed uuencoded MIME content. An attacker who can cause an application to handle a crafted email may crash the application or potentially run code.

mitigation

Do not rely on a specific upgrade target: the evidence does not identify a fixed version. Reduce exposure by blocking or quarantining uuencoded email content before VMime processes it, and update when a vendor-confirmed fixed 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.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 21:52Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-26 21:52Z
    ghsa: trigger signal, started the run
  2. 2026-10-26 21:52Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2710",
  "cve_id": "CVE-2026-116738",
  "display_id": "CVE-2026-116738",
  "ghsa_id": "GHSA-rhj9-fcgr-5r62",
  "euvd_id": "EUVD-2026-110486",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer underflow in VMime uuencoded MIME decoding",
  "summary": "VMime through 0.9.2 is affected when it processes malformed uuencoded MIME content. An attacker who can cause an application to handle a crafted email may crash the application or potentially run code.",
  "mitigation": "Do not rely on a specific upgrade target: the evidence does not identify a fixed version. Reduce exposure by blocking or quarantining uuencoded email content before VMime processes it, and update when a vendor-confirmed fixed release is available.",
  "vendor": "kisli",
  "product": "vmime",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.9.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "vmime",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.616250283333333,
  "t0_at": "2026-10-26T21:52:37.804000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T21:52:37.804000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T21:52:37.804000+00:00",
      "url": "https://github.com/advisories/GHSA-rhj9-fcgr-5r62"
    }
  }
}

published 2026-10-27 00:52Z
last change 2026-10-27 05:32Z

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.