Memory corruption via uninitialized iterator pointer
Published Feb 18, 2025 · Updated Apr 13, 2026
Memory corruption in Firefox before 135.0.1 allows remote attackers to crash the browser through crafted web content. UnsafePreContentIterator::Init can fail while leaving mCurNode uninitialized, and its failure is ignored before iteration over random or poison addresses. No authentication is required, and arbitrary code execution remains a vendor-stated presumption rather than a reproduced outcome.
Summary
What happened
Memory corruption in Firefox before 135.0.1 allows remote attackers to crash the browser through crafted web content. UnsafePreContentIterator::Init can fail while leaving mCurNode uninitialized, and its failure is ignored before iteration over random or poison addresses. No authentication is required, and arbitrary code execution remains a vendor-stated presumption rather than a reproduced outcome.
The record
- CVE
- CVE-2025-1414
- Published
- Feb 18, 2025
- Updated
- Apr 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 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.
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