BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-71393High confidence

Heap Buffer Overflow in GNU Emacs for Android

GNU · Emacs

5.3MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.67% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs GNU Emacs and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceemacsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourceemacsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourceemacsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourceemacsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsemacsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivexemacs21Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivexemacs21-packagesUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-55258

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

GNU Emacs for Android is vulnerable to an integer overflow in sfnt_read_name_table() in src/sfnt.c. The function computes an allocation size using a 32-bit length value from a TrueType font file without overflow checking. On 32-bit targets, a crafted font causes the calculation to wrap, resulting in an undersized heap allocation. A subsequent read() call writes beyond the buffer, causing a heap buffer overflow. 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 can lead to heap memory corruption and potential code execution. This issue was fixed in commit d51a4722316efe0960994d371e1859099894d1ca

What

GNU Emacs for Android is vulnerable to an integer overflow in sfnt_read_name_table() in src/sfnt.c. The function computes an allocation size using a 32-bit length value from a TrueType font file without overflow checking. On 32-bit targets, a crafted font causes the calculation to wrap, resulting in an undersized heap allocation. A subsequent read() call writes beyond the buffer, causing a heap buffer overflow. 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 can lead to heap memory corruption and potential code execution. This issue was fixed in commit d51a4722316efe0960994d371e1859099894d1ca

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

GNU Emacs for Android is vulnerable to an integer overflow in sfnt_read_name_table() in src/sfnt.c. The function computes an allocation size using a 32-bit length value from a TrueType font file without overflow checking. On 32-bit targets, a crafted font causes the calculation to wrap, resulting in an undersized heap allocation. A subsequent read() call writes beyond the buffer, causing a heap buffer overflow. 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 can lead to heap memory corruption and potential code execution. This issue was fixed in commit d51a4722316efe0960994d371e1859099894d1ca

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Integer Overflow or Wraparound → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-190 ↗

CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:L/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SILowSubsequent-system integrity: A successful attack can cause a limited loss.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-190
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2721GNU Emacs: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in GNU Emacs ausnutzen, um Informationen offenzulegen, um beliebigen Programmcode auszuführen, und um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT Polska · Polish · CVE-2026-71391CERT Polska w social mediach

CERT Polska otrzymał zgłoszenie o podatnościach w oprogramowaniu GNU Emacs i koordynował proces ujawniania informacji. Podatność CVE-2026-71391 : W oprogramowaniu GNU Emacs na urządzenia z systemem Android wykryto błąd typu off-by-one w parserze tabeli gvar (plik src/sfnt.c ). W funkcjach sfnt_vary_simple_glyph() i sfnt_vary_compound_glyph() sprawdzanie granic indeksu używa porównania „większy niż" zamiast „większy lub równy". W rezultacie spreparowany plik czcionki TrueType może ominąć weryfikację i wywołać odczyt poza granicami sterty za pomocą memcpy . Atakujący może dostarczyć złośliwy plik czcionki pocztą e-mail, przez EWW (Emacs Web Wowser) lub w dokumentach z niestandardowymi faces (mechanizm Emacs), co spowoduje załadowanie go przez Emacs. Ujawnia to zawartość pamięci sterty, która może zostać później wykorzystana do pokonania mechanizmu ASLR. Problem ten został rozwiązany w commicie 95ab9ef627b212d74d321c5bbb5b56a1be7b9fbe Podatność CVE-2026-71392 : W GNU Emacs na urządzeniach z systemem Android wykryto podatność typu integer overflow w funkcji sfnt_read_cmap_format_12() w pliku src/sfnt.c . W wersjach 32-bitowych, podczas przetwarzania spreparowanego pliku czcionki TrueType , niezabezpieczona operacja dodawania w wywołaniu xmalloc powoduje przepełnienie zmiennej. Skutkuje to zbyt małą alokacją bufora i zapisem poza jego granicami na stercie. Atakujący może dostarczyć złośliwy plik czcionki za pośrednictwem poczty e-mail, EWW lub dokumentów z niestandardowymi faces , co powoduje załadowanie go przez Emacs. Prowadzi to do uszkodzenia pamięci na stercie, co może prowadzić do wykonania kodu przez atakującego. Problem ten został rozwiązany w commicie c4e20777c26548722a37b03db93243e83a0d6188 Podatność CVE-2026-71393 : W oprogramowaniu GNU Emacs dla udządzeń Android zidentyfikowano podatność typu integer overflow w funkcji sfnt_read_name_table() w pliku src/sfnt.c . Funkcja ta odczytuje z pliku czcionki TrueType 32-bitową wartość długości i na jej podstawie oblicza rozmiar pamięci do alokacji, nie sprawdzając jednak, czy wynik mieści się w oczekiwanym przedziale wartości. Na architekturach 32-bitowych spreparowana czcionka może spowodować przepełnienie wyniku obliczeń, co skutkuje przydzieleniem zbyt małego bufora na stercie. Wywołanie funkcji read() zapisuje dane poza granicami tego bufora, co powoduje heap buffer overflow. Atakujący może dostarczyć złośliwy plik fontu za pomocą poczty e-mail, EWW lub dokumentów z niestandardowymi faces , co powoduje załadowanie go przez Emacs. Może to prowadzić do uszkodzenia pamięci na stercie i potencjalnego wykonania kodu przez atakującego. Problem ten został rozwiązany w commicie d51a4722316efe0960994d371e1859099894d1ca Podatność CVE-2026-71394 : Oprogramowanie GNU Emacs dla urządzeń Android nieprawidłowo weryfikuje dane nagłówka tabeli w funkcji sfnt_read_table_directory() w pliku src/sfnt.c . Z powodu użycia nieprawidłowej zmiennej do sprawdzania długości odczytu, spreparowany plik czcionki może zadeklarować więcej wpisów w katalogu tabeli, niż zawiera w rzeczywistości. W rezultacie parser zwraca strukturę, której wpisy katalogu tabeli zawierają niezainicjowane dane sterty. Atakujący może dostarczyć złośliwy plik czcionki pocztą e-mail, przez EWW lub w dokumentach z niestandardowymi faces , co powoduje załadowanie go przez Emacs. Prowadzi to do użycia niezainicjowanych danych sterty w kolejnych wyszukiwaniach w tabeli, co może prowadzić do ujawnienia informacji, awarii programu lub dowolnego dostępu do pamięci na platformach 32-bitowych. Problem ten został rozwiązany po commicie 7621ee1d01229d50e5c0cddea6bf0b01095a62cf

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Emacs: ≤ 30.2
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 10 Aug 2026, 17:50 UTC · CWE-190 · Integer Overflow or Wraparound

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-55258
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-71393 · cve.blacktree.nl