Firefox MobileWeb browser · Mozilla
CVE-2026-14906
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 · uneditedPages with malicious titles could potentially allow saved PDF content to overwrite PDF files or bundled content within the Firefox for iOS application sandbox. This vulnerability was fixed in Firefox for iOS 152.4.
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 confidenceFirefox for iOS contains a file overwrite vulnerability where malicious web pages with specially crafted titles can cause saved PDF content to overwrite files within the application's sandbox. This appears to be a path traversal or insufficient input sanitization issue in the PDF saving functionality where the page title is used to construct file paths without proper validation.
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
Firefox MobileWeb browser
< 152.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if Firefox for iOS is installedOpen the iOS Settings app, scroll down to Safari, then to Advanced, then to Experimental Features. Alternatively, check the App Library or search for 'Firefox' on the device.Affected if Firefox for iOS is present on the device
-
Determine the installed Firefox for iOS versionOpen the Firefox app, tap the menu (three lines or profile icon), tap Settings, scroll to the bottom where the app version is displayed under 'About Firefox iOS'.Affected if The displayed version is earlier than 152.4 (e.g., 152.3, 152.2, etc.)
-
Identify the PDF saving feature usageReview browser history or downloads folder for any PDF files saved from web pages. The vulnerability is triggered when saving a PDF from a maliciously crafted webpage.Affected if PDFs have been saved from web pages using Firefox for iOS on an affected version
A user is affected if Firefox for iOS version is lower than 152.4 and they have used the PDF saving feature from web pages.
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 · scoped152.4
Update to Firefox for iOS version 152.4 or later. Users should avoid saving PDFs from untrusted sources until the update is applied.
Firefox for iOS 152.4
- Open the App Store on your iOS device
- Search for Firefox for iOS
- Update Firefox to version 152.4 or later
- Ensure the update completes successfully before using the browser
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox Mobile
Scoped from the published advisory
- Consultation2.0 h
- Implementation5.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14906 — 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-14906 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