CVE-2026-115943
Description
A flaw was found in Spreadsheet::XLSX. This vulnerability can lead to arbitrary code execution when the library processes a spreadsheet containing crafted number format conditions. The module improperly evaluates workbook-supplied formatting conditions as code during file parsing. An attacker can exploit this flaw by providing a malicious spreadsheet file, potentially executing arbitrary commands with the privileges of the application processing the file.
Statement
This flaw is rated as Important severity because an attacker can achieve arbitrary code execution in the context of the running application by inducing it to parse an untrusted workbook, though successful exploitation relies on user interaction or services ingesting untrusted files. Red Hat Enterprise Linux does not include the perl-Spreadsheet-XLSX package in core distribution repositories, as it is only distributed through community channels such as Extra Packages for Enterprise Linux (EPEL). Consequently, enterprise environments are not exposed by default, limiting the potential attack surface to custom installations that explicitly integrate this Perl module.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.
Non-Repudiation
Technical Impact: Hide Activities
Often the actions performed by injected control code are unlogged.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
