10 matches found
EUVD-2026-37071
Denial-of-service in the Graphics: ImageLib component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
EUVD-2026-37080
Privilege escalation in the Graphics: WebRender component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
EUVD-2026-37081
Memory safety bug fixed in Firefox 152. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
CVE-2026-12328
Memory safety bugs present in Firefox ESR 115.36, Firefox ESR 140.11, Thunderbird ESR 140.11, Firefox 151 and Thunderbird 151. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This...
CVE-2026-12302
Mitigation bypass in the DOM: Security component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
CVE-2026-12295
Sandbox escape in the DOM: Navigation component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
CVE-2026-12297
Sandbox escape due to incorrect boundary conditions in the Networking component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, and Firefox ESR 115.37...
CVE-2026-12297
CVE-2026-12297 : Sandbox escape caused by incorrect boundary conditions in the Networking component of Firefox. Affected: Firefox and Firefox ESR. Mitigation: fixed in Firefox 152, ESR 140.12, and ESR 115.37. Exploitation status is not provided in the documents.
CVE-2026-12291 Use-after-free in the Networking: HTTP component
Use-after-free in the Networking: HTTP component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, Firefox ESR 115.37, Thunderbird 152, and Thunderbird 140.12...
CVE-2026-12290
The CVE-2026-12290 entry corresponds to a memory-safety bug addressed by Mozilla in Firefox 152, and corresponding ESR branches Firefox ESR 140.12 and Firefox ESR 115.37. The connected records confirm the vulnerability type as memory safety and state that the issue was fixed in the listed version...