FirefoxWeb browser · Mozilla
CVE-2026-2794
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInformation disclosure due to uninitialized memory in Firefox and Firefox Focus for Android. This vulnerability was fixed in Firefox 148.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUninitialized memory vulnerability in Firefox and Firefox Focus for Android allows information disclosure. The browser reads memory contents that weren't properly cleared before use, potentially exposing sensitive data from previous memory allocations to web content or the browser interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FirefoxWeb browser
< 148.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Firefox desktop versionOpen Firefox, click the menu icon (three lines), select Help, then About Firefox. The version number will be displayed on the page that opens.Affected if The displayed version is below 148.0 (such as 147.x, 147.0.x, or any earlier version)
-
Verify Firefox version via address barType 'about:support' in the Firefox address bar and press Enter. Look for the 'Version' field in the Application Basics section.Affected if The version shown is less than 148.0
-
Check if running an unpatched releaseCompare your installed Firefox version number against the affected range of any version below 148.0. Note that beta, nightly, and developer versions may also be affected if they predate the fix.Affected if Your installed version is 147.x, 146.x, or any older release, regardless of the specific minor or patch number
You are affected if Firefox is installed at any version below 148.0, since the vulnerability was fixed in version 148.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped148.0
Update to Firefox 148 or later for Android devices. This is a client-side browser vulnerability; users should ensure their mobile browser installations are patched to the latest version.
Firefox 148.0 (or later) for desktop and Firefox Focus for Android
- Open Firefox and navigate to Help > About Firefox to check the current version
- Download Firefox 148.0 from the official Mozilla website (www.mozilla.org)
- Run the downloaded installer to upgrade Firefox
- If automatic updates are enabled, the update should apply automatically on next restart
- After upgrading, verify the version by checking Help > About Firefox shows version 148.0 or later
- For Firefox Focus for Android, open the Google Play Store and update to the latest version which includes the Firefox 148 fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data