Quick answers
- Is CVE-2026-71391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71391 being exploited in the wild.
- How severe is CVE-2026-71391?
- Informational severity, with a CVSS score of 0, published 10 August 2026.
- Which products and versions are affected?
- Gnu Emacs through 30.2.
- Is there a fix for CVE-2026-71391?
- A patch was published on 2026-08-10: Fixed in commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71391 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-71391?
- Check whether you run Gnu Emacs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an off-by-one error (CWE-193) in the gvar table parser within src/sfnt.c in GNU Emacs for Android. The functions sfnt_vary_simple_glyph() and sfnt_vary_compound_glyph() use a strict greater-than comparison instead of greater-than-or-equal when validating shared-coordinate array indices, allowing an index equal to the boundary to pass the check. This permits a crafted TrueType variable font to trigger a heap-based out-of-bounds read via memcpy. An attacker can deliver the malicious font via email, web content (EWW), or documents with embedded custom faces. The exploit exposes heap memory contents that can defeat ASLR. The issue was fixed in commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe.
Affected products
- GNU Emacs through 30.2
Timeline
- 2026-08-10: disclosed
- 2026-08-10: patched: Fixed in commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe