xlnt-community xlnt up to 1.6.1 Encrypted XLSX File Parser compound_document.cpp read_directory out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in xlnt-community xlnt up to 1.6.1. The affected element 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. The manipulation leads to out-of-bounds.
This vulnerability is listed as CVE-2026-3664. The attack must be carried out locally. In addition, an exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in xlnt-community xlnt up to 1.6.1. This issue affects the function xlnt::detail::compound_document::read_directory of the file source/detail/cryptography/compound_document.cpp of the component Encrypted XLSX File Parser. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-3664. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept.
Applying the patch 147 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-10156). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CNA Base Score: 3.3
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 147
Timeline
03/06/2026 Advisory disclosed03/06/2026 VulDB entry created
03/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 141
Status: Confirmed
CVE: CVE-2026-3664 (🔒)
GCVE (CVE): GCVE-0-2026-3664
GCVE (VulDB): GCVE-100-349553
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/06/2026 21:39Updated: 03/12/2026 14:17
Changes: 03/06/2026 21:39 (60), 03/07/2026 22:24 (1), 03/08/2026 15:36 (30), 03/12/2026 14:17 (12)
Complete: 🔍
Submitter: Oneafter
Cache ID: 216:31F:103
Submit
Accepted
- Submit #764646: xlnt-community xlnt commit bceb706 and before Memory Corruption (by Oneafter)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.