Arbitrary code execution via memory corruption
Published Jun 24, 2025 · Updated Apr 13, 2026
Memory corruption in Mozilla Firefox and Thunderbird 139 allows attackers to execute arbitrary code via unspecified vectors. Mozilla groups five memory-safety defects under this identifier, but the individual code loci and unsafe operations are not publicly disclosed. Firefox is exposed in browser contexts; Thunderbird generally blocks email-based exploitation because scripting is disabled when reading mail.
Summary
What happened
Memory corruption in Mozilla Firefox and Thunderbird 139 allows attackers to execute arbitrary code via unspecified vectors. Mozilla groups five memory-safety defects under this identifier, but the individual code loci and unsafe operations are not publicly disclosed. Firefox is exposed in browser contexts; Thunderbird generally blocks email-based exploitation because scripting is disabled when reading mail.
The record
- CVE
- CVE-2025-6436
- Published
- Jun 24, 2025
- Updated
- Apr 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2025CVE publishedPublication date reported by the CVE source.
- Apr 13, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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