CVE-2026-113679
7.0HighPublished 20 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- None
- User interaction
- Required
- Impact
- Full C/I/A compromise
- Weakness
- CWE-787
Impact
Attackers can crash applications or corrupt host memory by tricking a user or service into loading a maliciously crafted font. Exploitation requires the target application to process untrusted fonts using the experimental WebAssembly shaper.
Root cause
The font_glyph_to_string import specifies an incorrect WAMR signature, allowing glyph-name data to write past linear memory boundaries into host space.
Affected systems
HarfBuzz 8.0.0 through 14.6.0
CVSS v3.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to a fixed HarfBuzz release past 14.6.0 containing commit 5e821de8256d01780566b5c8ab7886fae4c93da8, or disable the experimental WebAssembly shaper build option if patching immediately is not feasible.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
HarfBuzz 8.0.0 through 14.6.0 contains an out-of-bounds write vulnerability in the experimental WebAssembly shaper because the font_glyph_to_string import has a wrong WAMR signature. Attackers can supply a crafted font whose wasm module places the output buffer near linear memory's end, writing glyph-name bytes into host memory to crash or corrupt applications.
References
- https://github.com/harfbuzz/harfbuzz/blob/14.6.0/src/hb-wasm-api-font.hh#L115-L123
- https://github.com/harfbuzz/harfbuzz/blob/14.6.0/src/hb-wasm-api-list.hh#L85
- https://github.com/harfbuzz/harfbuzz/commit/5e821de8256d01780566b5c8ab7886fae4c93da8
- https://github.com/harfbuzz/harfbuzz/pull/6414
- https://www.vulncheck.com/advisories/harfbuzz-8.0.0-through-14.6.0-out-of-bounds-write-via-webassembly-font-glyph-to-string