Source: libvmime X-Debbugs-CC: [email protected] Severity: grave Tags: security
Hi, The following vulnerabilities were published for libvmime. CVE-2026-116738[0]: | VMime through 0.9.2 contains an integer underflow in the | uuEncoder::decode function that allows remote attackers to trigger a | stack-based buffer overflow via crafted uuencoded MIME parts. | Attackers can send an email with a uuencoded line whose length | character is 'b' but is not a 'begin' line, corrupting stack memory | to crash the application or potentially execute code. https://github.com/kisli/vmime/pull/363 Fixed by: https://github.com/kisli/vmime/commit/e85925eddc638939f0eeb7ee55ec047d04a760d8 CVE-2026-116739[1]: | VMime through 0.9.2 contains an information disclosure vulnerability | in the uuEncoder::decode function that writes uninitialized stack | memory into decoded output for over-long lines. Attackers can send a | crafted uuencode or x-uuencode MIME part with a large line length | byte to leak up to 15 bytes of stack contents per line in decoded | attachments. https://github.com/kisli/vmime/pull/363 Fixed by: https://github.com/kisli/vmime/commit/e85925eddc638939f0eeb7ee55ec047d04a760d8 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-116738 https://www.cve.org/CVERecord?id=CVE-2026-116738 [1] https://security-tracker.debian.org/tracker/CVE-2026-116739 https://www.cve.org/CVERecord?id=CVE-2026-116739 Please adjust the affected versions in the BTS as needed.

