Skip to main content
CVE-2024-30203VulnerabilityPublished Updated

CVE-2024-30203: emacs · n/a

Affects emacsSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 29.3 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 29.3
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade debian/emacs to 29.3.

Affected software

ProductAffectedFixed in
Debiandebian/emacspkg:deb/debian/emacsOther threatsAffected
  • <29.3
Fixed in
  • 29.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-30203, organizations should: 1) Upgrade Emacs to version 29.3 or later once the patch is officially released, as this will address the vulnerability in Gnus. 2) Until an update is available, restrict the use of Gnus for email handling, especially avoiding opening emails from untrusted or unknown sources. 3) Implement local security controls to limit user privileges and prevent unauthorized local access, reducing the risk of exploitation. 4) Educate users about the risks of opening suspicious emails and inline content within Emacs/Gnus. 5) Consider disabling or limiting the processing of inline MIME content in Gnus if configuration options allow. 6) Monitor Emacs and Gnus usage logs for unusual crashes or hangs that could indicate exploitation attempts. 7) Employ endpoint protection solutions that can detect anomalous application behavior. These steps go beyond generic advice by focusing on configuration, user education, and monitoring specific to the Emacs/Gnus environment.

Description

In Emacs before 29.3, Gnus treats inline MIME contents as trusted.

References

Community reviews

Loading reviews…