FirefoxWeb browser · Mozilla

CVE-2026-7324

HIGH · 7.3 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 150.0.1 or later.
See remediation →
82/100
Remediation priority · High
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
Memory safety bugs present in Thunderbird 150.0.0. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 150.0.1 and Thunderbird 150.0.1.

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

Memory safety bugs in Thunderbird 150.0.0 allowed memory corruption that could potentially be exploited for arbitrary code execution with sufficient effort. This is a classic memory safety vulnerability in the Mozilla browser engine.

MitigationUpgrade to Thunderbird 150.0.1 or Firefox 150.0.1 (or later) to patch the memory safety vulnerabilities.

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:< 150.0.1
ThunderbirdApplication
Affected:< 150.0.1

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 is installed
    Check for Firefox installation by looking for the executable. On Windows: check 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/bin/firefox.
    Affected if Firefox is present on the system
  2. Check Firefox installed version
    Run 'firefox --version' on Linux/macOS, or check the application properties on Windows. Alternatively, access about:firefox in the browser address bar.
    Affected if The reported version is less than 150.0.1
  3. Identify if Thunderbird is installed
    Check for Thunderbird installation. On Windows: check C:\Program Files\Mozilla Thunderbird\thunderbird.exe or C:\Program Files (x86)\Mozilla Thunderbird\thunderbird.exe. On macOS: check /Applications/Thunderbird.app. On Linux: run 'which thunderbird' or check /usr/bin/thunderbird.
    Affected if Thunderbird is present on the system
  4. Check Thunderbird installed version
    Run 'thunderbird --version' on Linux/macOS, or check the application properties on Windows. Alternatively, access about:thunderbird in the application.
    Affected if The reported version is less than 150.0.1

The environment is affected if any installed Firefox or Thunderbird version is below 150.0.1.

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

Upgrade to Thunderbird 150.0.1 or Firefox 150.0.1 (or later) to patch the memory safety vulnerabilities.

Recommended fix High confidence

Firefox 150.0.1 and Thunderbird 150.0.1

  1. Back up any important data, bookmarks, and settings from the current Firefox/Thunderbird installation
  2. Download Firefox 150.0.1 from the official Mozilla website (www.mozilla.org) or your organization's software distribution channel
  3. Download Thunderbird 150.0.1 from the official Mozilla website (www.mozilla.org) or your organization's software distribution channel
  4. Close all instances of Firefox and Thunderbird
  5. Install Firefox 150.0.1 by running the installer and following the prompts
  6. Install Thunderbird 150.0.1 by running the installer and following the prompts
  7. After installation, verify the version by navigating to Help > About Firefox and Help > About Thunderbird to confirm version 150.0.1 is installed
  8. Restart the applications and test that they function normally
Caveat Minor browser version upgrades typically do not introduce breaking changes; however, some extensions or add-ons may need updates for compatibility

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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