Xlnt Vulnerabilities

Security vulnerability tracking for Xlnt-community Xlnt

Last updated: Mar 7, 2026
Total CVEs

3

Critical

0

With Exploits

3

Last 30 Days

0

Vulnerability Timeline

3 vulnerabilities discovered over time for Xlnt

Severity Distribution

Critical0
0%
High0
0%
Medium3
100%
Low0
0%
DescriptionVendor / ProductExploit Status
CVE-2026-36654.8

This vulnerability allows an attacker to crash the xlnt application by causing it to access a part of memory that doesn't exist, leading to a program failure. The attacker must have local access to the system to exploit this issue, and there are publicly available methods to do so.

xlnt-communityxlnt
Exploit Available
about 1 month agoMar 7, 2026
CVE-2026-36644.8

This vulnerability allows an attacker to read sensitive data from memory by manipulating how the software processes encrypted XLSX files. However, the attack can only be carried out locally, meaning the attacker needs access to the system where the software is running.

xlnt-communityxlnt
Exploit Available
about 1 month agoMar 7, 2026
CVE-2026-36634.8

This vulnerability allows an attacker with local access to read beyond the intended limits of memory in the xlnt XLSX file parser, potentially exposing sensitive information. It is important to apply the provided patch to fix this issue, as the exploit has already been made public.

xlnt-communityxlnt
Exploit Available
about 1 month agoMar 7, 2026

About Xlnt-community Xlnt Security

This page provides comprehensive security vulnerability tracking for Xlnt-community Xlnt. Our database includes all CVEs affecting this product, updated in real-time from official sources.

Each vulnerability listing includes detailed CVSS severity analysis, exploit availability status, AI-generated explanations, and direct links to official security patches and vendor advisories.

Security Recommendations

  • • Always keep Xlnt updated to the latest version
  • • Subscribe to security advisories from Xlnt-community
  • • Monitor this page for new vulnerabilities affecting your version
  • • Prioritize patching critical and high severity issues immediately