# CVE-2026-63279: Out of bounds read in PICT image import

> An out-of-bounds read in LibreOffice's PICT image importer allows attackers to cause crashes or leak memory by providing a crafted image with an invalid palette index.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-63279, ECHO-088c-1462-ca4c, GHSA-v5cv-mqwj-8jgx, MINI-g295-55f8-2g9c, UBUNTU-CVE-2026-63279

## What is CVE-2026-63279?

CVE-2026-63279 is a medium-severity memory corruption vulnerability in The Document Foundation LibreOffice, published on 22 Sep 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 PICT images, which may be embedded in documents. An out of bounds read existed when importing an image that uses a colour palette. The palette index held in the image data was used without being checked against the number of entries the palette has, so an index past the last entry read memory outside the palette. In fixed versions the palette index is limited to the entries present.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-63279 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63279 is a medium-severity memory corruption vulnerability in The Document Foundation LibreOffice, published on 22 Sep 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-63279 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-63279/ (Markdown: https://insights.sbomify.com/CVE-2026-63279/index.md)
```

## Sources

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

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