CVE-2026-6047

Description

A flaw was found in LibreOffice. This vulnerability, a heap buffer overflow, occurs when processing specially crafted OOXML (Office Open XML) documents. An attacker could create a malicious document that, when opened, causes a write beyond the intended memory boundary during the replaying of deferred parser events for text box elements. This could lead to a denial of service, making the application unavailable.

Statement

This Moderate impact flaw in LibreOffice stems from a heap buffer overflow when handling specially crafted OOXML documents. Successful exploitation requires user interaction, where a victim must open a malicious document, resulting in a denial of service. This issue primarily affects application availability and does not facilitate arbitrary code execution or data exfiltration.

Mitigation

To mitigate this issue, users should exercise caution when opening untrusted or suspicious OOXML documents. Avoiding the opening of such documents from unknown sources can prevent the exploitation of this vulnerability. If possible, process untrusted documents in a sandboxed environment.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability,Integrity,Confidentiality

Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart

When a memory buffer is accessed using the wrong type, it could read or write memory out of the bounds of the buffer, if the allocated buffer is smaller than the type that the code is attempting to access, leading to a crash and possibly code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.