Security readout for executives and security teams
Plain-English summary
Mozilla reports a high-severity Android browser flaw where uninitialized memory could disclose information. The issue is named for Firefox and Firefox Focus for Android and was fixed in Firefox 148. The provided sources do not show active exploitation or a complete vulnerable version range.
Executive priority
Treat this as a near-term browser patching priority for Android fleets. It is high severity, but current provided evidence does not show known exploitation. Focus on confirming exposure and closing update gaps rather than emergency incident response.
Technical view
CVE-2026-2794 is classified as CWE-908, use of uninitialized resource. The CVSS 3.1 score is 7.5 with network attack vector, high complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impacts. Mozilla states the issue was fixed in Firefox 148.
Likely exposure
Exposure is most relevant to Android devices using Firefox or Firefox Focus. The bundle does not provide exact vulnerable version ranges, so teams should inventory installed Mozilla Android browser versions and compare them against Mozilla guidance for MFSA2026-13 and Firefox 148.
Exploitation context
The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates exploitation would require user interaction and high attack complexity, but could have high impact if successfully triggered.
Researcher notes
The bundle contains a mismatch: the affected entry lists Firefox version 148, while the description says the vulnerability was fixed in Firefox 148. Avoid assuming a vulnerable range without Mozilla advisory confirmation. Bugzilla and Red Hat references may contain additional product-status detail.
Mitigation direction
Update Firefox for Android to Firefox 148 or later where applicable.
Check Mozilla MFSA2026-13 for Firefox Focus for Android guidance.
Inventory managed and BYOD Android devices for Mozilla browser versions.
Use mobile device management to enforce browser updates where available.
Monitor Mozilla and Red Hat advisories for changed affected-version guidance.
Validation and detection
Confirm installed Firefox for Android versions are at least 148.
Check whether Firefox Focus for Android is present in device inventories.
Review Mozilla MFSA2026-13 for the final affected-product statement.
Verify no exception groups are pinned to older Android browser versions.
Document any devices awaiting vendor or app-store update availability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.