Memory corruption via WebRTC boundary error
Published Apr 21, 2026 · Updated Apr 21, 2026
Boundary-condition errors in Mozilla Firefox before 150 and Thunderbird before 150 allow remote attackers to corrupt process memory through WebRTC. Mozilla identifies the locus only as the WebRTC component; the access-restricted bug leaves the faulty boundary operation and resulting read, write, or crash behavior undisclosed. In Thunderbird, ordinary email reading generally disables scripting, so exploitation is generally limited to browser or browser-like contexts.
Summary
What happened
Boundary-condition errors in Mozilla Firefox before 150 and Thunderbird before 150 allow remote attackers to corrupt process memory through WebRTC. Mozilla identifies the locus only as the WebRTC component; the access-restricted bug leaves the faulty boundary operation and resulting read, write, or crash behavior undisclosed. In Thunderbird, ordinary email reading generally disables scripting, so exploitation is generally limited to browser or browser-like contexts.
The record
- CVE
- CVE-2026-6752
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 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