CVE-2026-41511 is a medium-severity (CVSS 6.2) CWE-835 vulnerability in OpenMcdf. A fix is available for OpenMcdf — see the affected versions and patch details below.
OpenMcdf has an Infinite loop DoS via crafted CFB directory cycle
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41511.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
OpenMcdfReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Summary
OpenMcdf does not detect cycles in the directory entry red-black tree of a Compound File Binary (CFB) document. A crafted CFB file with a cycle in the LeftSiblingID / RightSiblingID chain causes Storage.EnumerateEntries() and Storage.OpenStream() to loop indefinitely, consuming the calling thread with no possibility of recovery via try/catch.
Details
CFB directory entries form a red-black tree linked by LeftSiblingID and RightSiblingID fields. OpenMcdf's DirectoryTreeEnumerator and DirectoryTree.TryGetDirectoryEntry traverse this tree without tracking visited node IDs, so a crafted cycle (e.g. entry A's RightSiblingID points to entry B, and entry B's LeftSiblingID points back to entry A) causes traversal to loop indefinitely.
Two distinct code paths are affected:
Storage.EnumerateEntries()-DirectoryTreeEnumerator.MoveNext()never returnsfalse; the same entry is yielded on every iteration and the caller'sforeachnever exits. Heap grows unboundedly as entries accumulate.Storage.OpenStream()-DirectoryTree.TryGetDirectoryEntryloops indefinitely insideDirectoryEntries.TryGetSiblingduring the name lookup.
PoC
A crafted CFB file with a sibling cycle (see attached) triggers the issue with the following code:
using OpenMcdf;
using var ms = new MemoryStream(File.ReadAllBytes("crafted.cfb"));
using var root = RootStorage.Open(ms);
// Never returns - EnumerateEntries loops indefinitely
foreach (var entry in root.EnumerateEntries())
{
Console.WriteLine(entry.Name);
if (entry.Type == EntryType.Stream)
root.OpenStream(entry.Name); // also hangs depending on the cycle structure
}
Impact
A denial of service affecting any application that opens untrusted CFB files with OpenMcdf. A small crafted input carrying a valid CFB magic header (D0 CF 11 E0 A1 B1 1A E1) is sufficient to pass initial format validation and reach the vulnerable traversal code. No exception is thrown, so try/catch cannot protect callers. The affected thread is unrecoverable without killing the process.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | OpenMcdf | all versions | 3.1.3dotnet add package OpenMcdf --version 3.1.3 |
Affected Products
openmcdfopenmcdfDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OpenMcdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update OpenMcdf to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41511 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2026-41511 in your dependencies?
Find it across NuGet, including transitive dependencies.