CVE-2026-6776
Boundary Error in Firefox WebRTC Networking Causes Potential Exploit
Publication date: 2026-04-21
Last updated on: 2026-04-22
Assigner: Mozilla Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mozilla | firefox | to 150.0 (exc) |
| mozilla | firefox | to 140.10.0 (exc) |
| mozilla | thunderbird | to 140.10.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves incorrect boundary conditions in the WebRTC Networking component of Mozilla Firefox. It means that the software did not properly handle certain limits or edges in the network communication code, which could potentially lead to unexpected behavior or security issues. The problem was addressed and fixed in Firefox version 150 and Firefox ESR 140.10.
How can this vulnerability impact me? :
Incorrect boundary conditions in a networking component like WebRTC could potentially lead to security risks such as crashes, data leaks, or unauthorized access during real-time communications. However, specific impacts are not detailed in the provided information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
There is no information provided about how this vulnerability affects compliance with standards or regulations such as GDPR or HIPAA.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Firefox browser to version 150 or later, or Firefox ESR to version 140.10 or later, where the issue has been fixed.