FirefoxWeb browser · Mozilla

CVE-2026-24868

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 147.0.2 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
Mitigation bypass in the Privacy: Anti-Tracking component. This vulnerability was fixed in Firefox 147.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 · moderate confidence

A mitigation bypass in Firefox's Privacy: Anti-Tracking component allowed trackers to circumvent the anti-tracking protections. This represents a security control failure where intended privacy protections could be evaded by malicious actors.

MitigationUpdate Firefox to version 147.0.2 or later to apply the fix. Organizations should ensure browser update policies are enforced.

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:< 147.0.2

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. Verify Firefox is installed
    Check for Firefox executable: On Windows, look for 'C:\Program Files\Mozilla Firefox\firefox.exe' or 'C:\Program Files (x86)\Mozilla Firefox\firefox.exe'. On macOS, check '/Applications/Firefox.app'. On Linux, run 'which firefox' or check /usr/lib/firefox/
    Affected if Firefox is not installed on the system
  2. Determine installed Firefox version
    Open Firefox, click the menu (three horizontal lines), select Help, then About Firefox. Alternatively, run 'firefox --version' from command line. On Windows, right-click the executable and view Properties > Details for version info.
    Affected if The displayed version number is less than 147.0.2 (for example, 147.0, 146.x, 145.x, etc.)
  3. Confirm anti-tracking protection is enabled
    In Firefox address bar, type 'about:preferences' and press Enter. Scroll to the Privacy & Security section. Under Enhanced Tracking Protection, verify the setting is not disabled or set to 'Off'. The protection must be actively enabled for the bypass to apply.
    Affected if Enhanced Tracking Protection is set to 'Strict' or 'Standard' and the Firefox version is below 147.0.2

You are affected if Firefox version is below 147.0.2 AND Enhanced Tracking Protection is enabled (the bypass only matters when the protection is actually active).

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

Update Firefox to version 147.0.2 or later to apply the fix. Organizations should ensure browser update policies are enforced.

Recommended fix High confidence

Firefox 147.0.2 (or ESR 127.x if applicable to your deployment)

  1. Open Firefox and navigate to Help > About Firefox (or go to Menu > Help > About Firefox)
  2. In the About Firefox window, Firefox will automatically check for and download the latest version
  3. Click 'Restart to Update Firefox' when the update is ready
  4. Alternatively, download Firefox 147.0.2 directly from the official Mozilla website: https://www.mozilla.org/en-US/firefox/releases/
  5. If using an enterprise deployment, use the ESR version matching 147.0.2 or apply via your management tooling

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24868 — 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-2026-24868 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