# CVE-2026-113680: HarfBuzz 8.0.0 through 14.6.0 WebAssembly Shaper NULL Pointer Dereference DoS


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109809, DEBIAN-CVE-2026-113680, ECHO-a5d1-e1b2-a5a5, GHSA-2fqx-2h7j-c7gq, UBUNTU-CVE-2026-113680

## What is CVE-2026-113680?

CVE-2026-113680 is a medium-severity vulnerability in harfbuzz, published on 20 Oct 2026. 

### Official description

HarfBuzz from 8.0.0 through 14.6.0 contains a NULL pointer dereference vulnerability in the experimental WebAssembly shaper host imports buffer_set_contents, face_create, and font_set_coords. Attackers can supply a crafted font whose embedded wasm module passes out-of-range addresses with non-zero lengths, crashing any application that shapes text with the font.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

No fix has been published for CVE-2026-113680 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113680 is a medium-severity vulnerability in harfbuzz, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113680 in the wild and no public exploit code.

Affected product: harfbuzz. 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-113680/ (Markdown: https://insights.sbomify.com/CVE-2026-113680/index.md)
```

## Sources

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

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