# CVE-2026-63275: Stack buffer overflow in CFF font hint handling

> A stack buffer overflow in LibreOffice's CFF font hint handling allows attackers to execute arbitrary code or cause a crash via malicious documents.

- **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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-63275, ECHO-0c4c-8c22-be6a, GHSA-fh9h-5g6m-wc43, MINI-r5f9-v9fw-f59q, UBUNTU-CVE-2026-63275

## What is CVE-2026-63275?

CVE-2026-63275 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 read CFF fonts, which may be embedded in documents. A stack buffer overflow existed when reading the hints of a glyph. The number of hints was checked against the wrong bound, so a glyph declaring more hints than the array can hold wrote past its end. In fixed versions the hint count is checked against the capacity the array really has.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-63275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63275 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-63275 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-63275/ (Markdown: https://insights.sbomify.com/CVE-2026-63275/index.md)
```

## Sources

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

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