Code execution via undisclosed memory corruption
Published Oct 1, 2024 · Updated Nov 3, 2025
Memory corruption in Firefox before 131, Firefox ESR before 115.16 or 128.3, and Thunderbird before 128.3 or 131 allows attackers to run code. Mozilla groups four memory-safety defects under this identifier; some corrupt memory, but their code loci, triggering inputs, and faulty operations are undisclosed. The triggering vector is undisclosed; Thunderbird disables scripting while reading email, so ordinary message viewing does not expose the browser-like context.
Summary
What happened
Memory corruption in Firefox before 131, Firefox ESR before 115.16 or 128.3, and Thunderbird before 128.3 or 131 allows attackers to run code. Mozilla groups four memory-safety defects under this identifier; some corrupt memory, but their code loci, triggering inputs, and faulty operations are undisclosed. The triggering vector is undisclosed; Thunderbird disables scripting while reading email, so ordinary message viewing does not expose the browser-like context.
The record
- CVE
- CVE-2024-9401
- Published
- Oct 1, 2024
- Updated
- Nov 3, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-119, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <131
- Affected versionversion=unspecified <131
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo