FirefoxWeb browser · Mozilla
CVE-2026-3845
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 · uneditedHeap buffer overflow in the Audio/Video: Playback component in Firefox for Android. This vulnerability was fixed in Firefox 148.0.2.
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 · high confidenceA heap buffer overflow vulnerability exists in the Audio/Video Playback component of Firefox for Android. This memory corruption flaw could allow an attacker to execute arbitrary code or cause denial of service via specially crafted media content. The issue was addressed in Firefox version 148.0.2.
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.0.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 for Android versionOpen Firefox for Android, tap the three-dot menu, scroll down to Settings, then tap 'About Firefox' to display the version numberAffected if The displayed version number is lower than 148.0.2 (for example, 148.0.1, 148.0, 147.x, or earlier)
-
Verify the product is Firefox for AndroidConfirm you are using Mozilla Firefox on an Android device, not Firefox for iOS, Firefox Focus, or Firefox DesktopAffected if The application is Firefox for Android (the vulnerability specifically affects the Android version)
-
Confirm media playback is accessibleVerify that the Firefox for Android browser can access and play media content (audio or video files or streams)Affected if Media playback functionality is available in the browser (the vulnerability exists in the Audio/Video Playback component)
You are affected if you are running Firefox for Android with a version lower than 148.0.2 on a device where media content can be played in the browser.
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.2
Update Firefox for Android to version 148.0.2 or later to apply the patched version containing the fix for this heap buffer overflow.
Firefox 148.0.2
- 1. Open Firefox on your Android device
- 2. Navigate to Menu > Settings > About Firefox
- 3. If your version is below 148.0.2, tap 'Update' to download and install the latest version
- 4. Alternatively, open the Google Play Store, search for Firefox, and update if version 148.0.2 or later is available
- 5. After installation, restart Firefox to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3845 — 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-3845 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