dbcve.org
FirefoxWeb browser · Mozilla

CVE-2025-1941

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 136.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Under certain circumstances, a user opt-in setting that Focus should require authentication before use could have been be bypassed (distinct from CVE-2025-0245). This vulnerability was fixed in Firefox 136.

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 confidence

Firefox Focus contains a security control bypass vulnerability where a user opt-in authentication requirement could be circumvented under certain circumstances. This allows unauthorized access to the browser without the intended authentication protection, despite the user having enabled this security setting. The vulnerability has a critical CVSS score of 9.1 due to the complete bypass of an intended security control.

MitigationOrganizations should ensure all Firefox Focus installations are updated to version 136 or later. IT departments should verify deployment of the patched version across all managed devices and confirm the authentication opt-in setting is functioning as intended.

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
Affected:< 136.0

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Firefox Focus installation
    Check device for Firefox Focus app (icon shows 'Focus' with a red fox head). On Android, go to Settings > Apps > Mozilla Firefox Focus. On iOS, go to Settings > General > iPhone Storage > Firefox Focus.
    Affected if Firefox Focus is installed on the device
  2. Determine installed version
    On Android: Settings > Apps > Mozilla Firefox Focus > App info > Version. On iOS: Long-press app icon > App Info > Version. Compare the version number to 136.0.
    Affected if Installed version is lower than 136.0 (e.g., 135.x, 135.0, 134.x, etc.)
  3. Verify authentication protection setting
    Open Firefox Focus > Tap menu (three dots) > Settings > Privacy and Security > confirm 'Require Authentication' or 'Lock on Startup' is enabled. The bypass only affects users who have enabled this protection.
    Affected if Authentication requirement is enabled AND version is below 136.0
  4. Check for recent browser usage
    Review browser history or recent tabs in Firefox Focus. If unauthorized access is suspected, there may be unexpected browsing history or saved sites.
    Affected if Unexpected browser activity exists after enabling authentication lock

User is affected if Firefox Focus version is below 136.0 AND the authentication protection setting was enabled, as the bypass allows unauthorized access despite the security setting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 136.0 or later
Fixed in 136.0
Interim mitigation

Organizations should ensure all Firefox Focus installations are updated to version 136 or later. IT departments should verify deployment of the patched version across all managed devices and confirm the authentication opt-in setting is functioning as intended.

Recommended fix High confidence

Firefox 136.0 or later

  1. Open Firefox and navigate to Menu > Help > About Firefox (or go to about:support)
  2. Check the current version number displayed
  3. If the version is below 136.0, click 'Restart to update Firefox' if an update is available, or download Firefox 136.0 from the official Mozilla website at https://www.mozilla.org/firefox/
  4. After updating, verify the version is 136.0 or later by returning to Menu > Help > About Firefox
  5. For Firefox Focus mobile users, update the app through the App Store (iOS) or Google Play Store (Android) to the latest version containing the 136.0 security fixes

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1941 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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