Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY7 SECURITY RECORDS

gnu

emacs

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at emacs, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-96269 22 Sep 2026 Emacs: 28.1 ≤ 31.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-77219 21 Aug 2026 Emacs: < 31.0.91 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-71394 10 Aug 2026 ≤ 30.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71393 10 Aug 2026 ≤ 30.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71392 10 Aug 2026 ≤ 30.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71391 10 Aug 2026 ≤ 30.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53920 27 Nov 2024 emacs: 30.0.92 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.