CVE-2026-71391

Off-by-One Error in GNU Emacs for Android

Published Aug 10, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
GNU Emacs for Android contains an off-by-one error in the gvar table parser in src/sfnt.c. The shared-coordinate index boundary check in sfnt_vary_simple_glyph() and sfnt_vary_compound_glyph() uses a strict greater-than comparison instead of greater-than-or-equal, allowing a crafted TrueType variable font to bypass the check and trigger a heap-based out-of-bounds read via memcpy. An attacker can deliver a malicious font file via email, EWW (Emacs Web Wowser), or documents with custom faces, causing Emacs to load it. This exposes heap memory contents which can be later used to defeat ASLR.


This issue was fixed in commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe

Analysis

AI-generated

Technical impact

An off-by-one error in GNU Emacs for Android’s gvar table parser allows a malicious TrueType variable font to skip a shared‑coordinate index boundary check. This results in a heap‑based out‑of‑bounds read that can leak heap contents, which an attacker may use to defeat address space layout randomization.

Affected Systems

All GNU Emacs for Android installations that have not applied the fix committed as 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe. No specific version line numbers are listed, so any pre‑fix instance is potentially vulnerable.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity. EPSS data is unavailable and the vulnerability is not listed in CISA’s KEV catalog, suggesting it is not currently a widely used exploit. Attacks require delivery of a crafted font file through email, the Emacs Web Wowser, or document files that Emacs processes. The open‑source nature of the software means that the vulnerability is easily reproducible, but no documented exploits are known. The primary risk is the exposure of heap memory that can undermine ASLR protections.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update GNU Emacs for Android to a version that includes commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe, which corrects the off‑by‑one check in sfnt.c
  • Configure Emacs to reject or sanitize variable fonts before loading them, reducing the chance of OOB reads through crafted TrueType files
  • Consider disabling custom face loading or periodic font cache clearing if an update is not immediately available, to limit exposure to malicious font inputs

Generated by OpenCVE AI on August 10, 2026 at 11:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N'}

threat_severity

Low

Type Values Removed Values Added
Description GNU Emacs for Android contains an off-by-one error in the gvar table parser in src/sfnt.c. The shared-coordinate index boundary check in sfnt_vary_simple_glyph() and sfnt_vary_compound_glyph() uses a strict greater-than comparison instead of greater-than-or-equal, allowing a crafted TrueType variable font to bypass the check and trigger a heap-based out-of-bounds read via memcpy. An attacker can deliver a malicious font file via email, EWW (Emacs Web Wowser), or documents with custom faces, causing Emacs to load it. This exposes heap memory contents which can be later used to defeat ASLR. This issue was fixed in commit 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe
Title Off-by-One Error in GNU Emacs for Android
First Time appeared Gnu
Gnu emacs
Weaknesses CWE-193
CPEs cpe:2.3:a:gnu:emacs:*:*:android:*:*:*:*:*
Vendors & Products Gnu
Gnu emacs
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
CERT-PL
Published
Updated
Aug 10, 2026, 5:48 PM
Reserved
Aug 6, 2026, 9:25 AM
Status
Deferred
Published
Aug 10, 2026, 11:17 AM
Modified
Oct 24, 2026, 3:10 PM
Severity
Low
Public date
Aug 10, 2026, 10:22 AM