# CVE-2026-6047: Heap buffer overflow in OOXML text box element import

> A heap buffer overflow in LibreOffice's OOXML text box import allows attackers to execute arbitrary code or cause a crash via a malicious document.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-6047, GHSA-wq72-h3fh-w757, UBUNTU-CVE-2026-6047

## What is CVE-2026-6047?

CVE-2026-6047 is a medium-severity memory corruption vulnerability in The Document Foundation LibreOffice, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

LibreOffice can import documents in the OOXML format (DOCX). A heap buffer overflow existed when replaying deferred parser events for a text box element. A handler object was assumed to be of one type and written to at that type's field layout, but it could be a smaller object, so the write landed past the end of the allocation. In fixed versions the type is checked before the write.

Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-6047?


## How do I fix CVE-2026-6047?

Apply the vendor's patch.

## Is CVE-2026-6047 being exploited?

There is no known exploitation of CVE-2026-6047 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6047 and fix it if it is affected.

What it is: CVE-2026-6047 is a medium-severity memory corruption vulnerability in The Document Foundation LibreOffice, published on 15 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6047 in the wild and no public exploit code.

Affected product: The Document Foundation LibreOffice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6047/ (Markdown: https://insights.sbomify.com/CVE-2026-6047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6047
- OSV: https://osv.dev/vulnerability/CVE-2026-6047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6047/
Summaries are generated and may contain mistakes; the official description above is the record.