FirefoxWeb browser · Mozilla

CVE-2025-9186

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-19
Fix available
A fix is available. Upgrade to 142.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Spoofing issue in the Address Bar component of Firefox Focus for Android. This vulnerability was fixed in Firefox 142.

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 confidence

A URL spoofing vulnerability existed in the Address Bar component of Firefox Focus for Android that could allow an attacker to display a misleading URL in the address bar while the user navigates to a different site. This is a client-side UI spoofing issue that was addressed in Firefox version 142.

MitigationUsers should update Firefox Focus for Android to version 142 or later to receive the security patch. Organizations should ensure mobile devices have automatic updates enabled or deploy the updated version through MDM.

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:< 142.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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 if Firefox Focus for Android is installed
    Open the device Settings > Apps > search for 'Firefox Focus' or 'Firefox', or check the app drawer for the Firefox Focus icon. Confirm the app name is specifically 'Firefox Focus' for Android.
    Affected if The app 'Firefox Focus for Android' is present on the device.
  2. Locate the installed version number
    Go to Settings > Apps > Firefox Focus > App info, or tap the three-dot menu in Firefox Focus and navigate to Help > About Firefox Focus. The version number is displayed (e.g., 141.1, 140.0.3).
    Affected if A version number is displayed that can be compared against the affected range.
  3. Compare version against affected range
    Check if the installed version is any build number less than 142.0 (such as 141.x, 140.x, 139.x, etc.). Note that version 142.0 and later are not affected.
    Affected if The installed version is below 142.0 (e.g., 141.1, 140.0.3, 139.0).

A user is affected if Firefox Focus for Android is installed with a version number lower than 142.0, as the URL spoofing vulnerability in the Address Bar component exists in those versions.

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 142.0 or later
Fixed in 142.0
Interim mitigation

Users should update Firefox Focus for Android to version 142 or later to receive the security patch. Organizations should ensure mobile devices have automatic updates enabled or deploy the updated version through MDM.

Recommended fix High confidence

Firefox 142.0 (or later) for Android

  1. Open the Google Play Store on your Android device
  2. Search for Firefox Focus (or Firefox browser if targeting the main browser)
  3. Tap the Update button to install version 142.0 or later
  4. Alternatively, go to Settings > Apps > Firefox Focus (or Firefox) > Check for updates
  5. After updating, verify the version by opening the app, tapping the menu, selecting Help or About, and confirming the version number is 142.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9186 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9186 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