CVE-2026-2794: Mozilla Firefox uninitialized memory disclosure in ContentParent

CVE-2026-2794 · Severity: high · CVSS 7.5 · Published 2026-02-24

A security vulnerability has been identified in the Firefox and Firefox Focus web browsers for Android. This flaw could allow a malicious website or a compromised internal process to access sensitive information stored in the device's memory that should otherwise be protected. This could lead to the exposure of private user data or help an attacker bypass security protections designed to keep different parts of the browser isolated.

Technologies: Mozilla Firefox, Mozilla Firefox Focus for Android. Vendors: Mozilla.

Quick answers

Is CVE-2026-2794 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-2794 being exploited in the wild.
How severe is CVE-2026-2794?
High severity, with a CVSS score of 7.5, published 24 February 2026.
Which products and versions are affected?
Mozilla Firefox < 148; Mozilla Firefox Focus for Android < 148; Mozilla GeckoView < 148.
Is there a fix for CVE-2026-2794?
A patch was published on 2026-02-24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-2794 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-2794?
Check whether you run Mozilla Firefox, Mozilla Firefox Focus for Android or Mozilla GeckoView at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An information disclosure vulnerability exists in Mozilla Firefox and Firefox Focus for Android within the 'ContentParent::RecvGetIconForExtension' function. The root cause is the use of uninitialized memory (CWE-908); the function allocates a buffer using 'AppendElements', which does not zero-initialize memory for uint8_t types. If a subsequent size check in 'AndroidBridge::GetIconForExtension' fails, the buffer is returned to the child process without being populated, effectively leaking raw parent process heap memory. A compromised child process can exploit this to achieve a sandbox escape or read sensitive data from the parent process. The issue is resolved in Firefox 148 by ensuring the buffer is properly initialized.

Affected products

  • Mozilla Firefox < 148
  • Mozilla Firefox Focus for Android < 148
  • Mozilla GeckoView < 148

Timeline

  • 2026-02-24: disclosed
  • 2026-02-24: advisory
  • 2026-02-24: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.