CVE-2026-8357: Heap buffer overflow in Calc formula compilation
LibreOffice Calc compiles cell formulas when opening a spreadsheet. A heap buffer overflow existed when compiling a very long formula made up of many opening tokens. The array that tracks nesting depth was allocated one element too small for that worst case, so such a formula wrote one element past its end. In fixed versions the array is sized to hold the largest possible nesting.
Security readout for executives and security teams
Plain-English summary
A crafted spreadsheet can trigger a memory corruption bug when LibreOffice Calc compiles an unusually long formula. Successful exploitation requires someone to open the file, but the CVSS impact is high for confidentiality, integrity, and availability.
Executive priority
Treat as high priority for fleets that handle external spreadsheets. Business urgency is highest where finance, operations, HR, or customer-service teams routinely open third-party spreadsheet files.
Technical view
CVE-2026-8357 is a heap buffer overflow in LibreOffice Calc formula compilation. A nesting-depth tracking array was allocated one element too small for worst-case formulas with many opening tokens, allowing a one-element out-of-bounds write. Sources list LibreOffice 26.2 as affected with unknown default status.
Likely exposure
Primary exposure is user workstations, VDI hosts, or document-processing systems where LibreOffice Calc 26.2 opens spreadsheets from email, downloads, portals, or third parties. The CVSS vector requires local file handling and user interaction, not direct network reachability.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation. The plausible attack path is social delivery of a crafted spreadsheet that a user opens in Calc. No exploit code or weaponized procedure is needed to assess exposure.
Researcher notes
Evidence supports a heap overflow caused by an off-by-one allocation during formula compilation. The source bundle does not identify active exploitation, exploit maturity, or exact fixed LibreOffice version names, so validation should stay tied to vendor advisories and package metadata.
Mitigation direction
Check LibreOffice and Red Hat advisories for fixed versions or packages.
Prioritize updating systems with LibreOffice Calc 26.2 installed.
Limit opening untrusted spreadsheets until patched.
Use sandboxed document handling for externally sourced spreadsheets.
Review Red Hat errata if using affected enterprise packages.
Validation and detection
Inventory endpoints and servers for LibreOffice Calc 26.2.
Confirm whether vendor-fixed LibreOffice or distribution packages are installed.
Check email, web upload, and shared-drive workflows handling spreadsheets.
Verify document-processing automation does not open untrusted spreadsheets unsandboxed.
Track the CVE against vendor advisories and Red Hat VEX status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-131: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-131 · source CWE mapping
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.