Skip to main content
Public proof of concept

CVE-2026-111145

ytnef through 2.1.2 Heap Out-of-Bounds Read via DecompressRTF

A public proof of concept exists; no exploitation attested.

  • Published2026-10-15
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

ytnef through 2.1.2 contains a heap out-of-bounds read vulnerability in DecompressRTF() in lib/ytnef.c that never validates uncompressedSize for uncompressed RTF streams. Attackers can supply a crafted winmail.dat TNEF attachment with a malicious PT_BINARY MAPI property to crash ytnefprint or libytnef callers and leak adjacent heap memory.

Timeline

dates in UTC
  1. 2026-10-1519:17CVE publishedNVD

Versions per branch

Products declared by the CNA1 product

As VulnCheck, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-15

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libytnefUbuntu:26.10all versions · no fixed version listed
  • libytnefUbuntu:26.04:LTSall versions · no fixed version listed
  • libytnefUbuntu:24.04:LTSall versions · no fixed version listed
  • libytnefUbuntu:22.04:LTSall versions · no fixed version listed
  • libytnefUbuntu:20.04:LTSall versions · no fixed version listed
  • libytnefUbuntu:18.04:LTSall versions · no fixed version listed
  • libytnefUbuntu:16.04:LTSall versions · no fixed version listed
  • libytnefDebian:14all versions · no fixed version listed

2 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-10-21
  • CNACVSS 4.06.9known since 2026-10-23
  • CNACVSS 3.16.1known since 2026-10-23
  • CNAweakness (CWE)CWE-125known since 2026-10-23
  • FIRST EPSSEPSS score0.1 %2026-11-08
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
CVSS 4.0 vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-10-15
Last Modified
2026-10-21
NVD status
Deferred
GitHub Advisory
GHSA-hjxh-c649-gvhr

Frequently asked questions

What is CVE-2026-111145?

ytnef through 2.1.2 contains a heap out-of-bounds read vulnerability in DecompressRTF() in lib/ytnef.c that never validates uncompressedSize for uncompressed RTF streams. Attackers can supply a crafted winmail.dat TNEF attachment with a malicious PT_BINARY MAPI property to crash ytnefprint or libytnef callers and leak adjacent heap memory.

Is CVE-2026-111145 actively exploited?

A proof-of-concept exploit exists for CVE-2026-111145, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-111145?

CVE-2026-111145 has a CVSS v3 base score of 6.1 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H.

Running libytnef? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record