CVE-2026-3664 xlnt-community xlnt Encrypted XLSX File compound_document.cpp read_directory out-of-bounds

Medium 4.8 Published Updated

An out-of-bounds read in the xlnt library's encrypted XLSX parser allows attackers to cause denial of service or disclose information via malicious files.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-3664?

CVE-2026-3664 is a medium-severity memory corruption vulnerability in xlnt-community xlnt, published on 7 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

A vulnerability was determined in xlnt-community xlnt up to 1.6.1. Impacted is the function xlnt::detail::compound_document::read_directory of the file source/detail/cryptography/compound_document.cpp of the component Encrypted XLSX File Parser. Executing a manipulation can lead to out-of-bounds read. The attack is restricted to local execution. The exploit has been publicly disclosed and may be utilized. This patch is called 147. Applying a patch is advised to resolve this issue.

Weakness: CWE-125, CWE-119

Which versions are affected by CVE-2026-3664?

It affects 1 product.

Products include Xlnt-Community Xlnt.

How do I fix CVE-2026-3664?

No fix has been published for CVE-2026-3664 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-3664 being exploited?

There is no known exploitation of CVE-2026-3664 in the wild and no public exploit code.

Sources

Also known as GHSA-3f3c-wc35-5wjv.

Is CVE-2026-3664 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free