Skip to content
High-Risk CVE-2026-116738 in VMime Library Allows Remote Code Execution

High-Risk CVE-2026-116738 in VMime Library Allows Remote Code Execution

First seen 27 Oct 2026, 02:14 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 27, 2026 at 08:13 UTC
  • •CVE-2026-116738 affects VMime library version 0.9.2 and earlier.
  • •Attackers can exploit this vulnerability via crafted uuencoded email parts.
  • •Immediate patching is recommended to prevent potential remote code execution.

A vulnerability, CVE-2026-116738, has been identified in the VMime library version 0.9.2, which contains an integer underflow in the uuEncoder::decode function. This flaw allows remote attackers to trigger a stack-based buffer overflow by sending crafted uuencoded MIME parts. The vulnerability affects systems that parse untrusted email, particularly internet-facing mail gateways and automated ingestion pipelines. Attackers can exploit this flaw without user interaction, potentially leading to application crashes or remote code execution. The CVSS score for this vulnerability is 8.7, indicating a high severity level. A patch has been released, and users are advised to upgrade immediately to mitigate the risk. Monitoring for decoder crashes and unusual memory faults is recommended until systems are patched. The vulnerability was published on October 26, 2026.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-26
CVE-2026-116738 published
The vulnerability was disclosed with a CVSS score of 8.7, indicating high severity.
Redpacketsecurity
2026-10-27
Vulnerability details and impact analysis released
Detailed analysis of the vulnerability's impact on email processing systems was published.
hackmd.io

More articles in this cluster (5)

Following this threat?

Track CVE-2026-116738 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of VMime are affected?
VMime versions 0.9.2 and all earlier releases are affected.
What should I do if I use VMime?
Upgrade to the patched release immediately to mitigate the risk of exploitation.
How can I detect exploitation attempts?
Monitor for decoder crashes, restarts, and inspect logs for malformed uuencoded parts.