Safeguard
Vulnerability Analysis•

CVE-2026-4692: Critical Sandbox Escape in Firefox

CVE-2026-4692: a sandbox escape in the Responsive Design Mode component in Firefox and Thunderbird. Fixed in Firefox 149, so update and check your version.

Safeguard Security Team
3 min read

CVE-2026-4692 is a sandbox escape in the Responsive Design Mode component in Firefox and Thunderbird. The NVD record scores it CVSS 10.0 (critical), while Mozilla rates it High. Mozilla fixed it in Firefox 149, Firefox ESR 115.34, Firefox ESR 140.9, Thunderbird 149 and Thunderbird 140.9. Update to those versions or later, and check bundled copies too.

What's affected

The NVD record lists Mozilla Firefox and Thunderbird as affected, and the description says the vulnerability was fixed in the following releases:

  • Firefox 149
  • Firefox ESR 115.34
  • Firefox ESR 140.9
  • Thunderbird 149
  • Thunderbird 140.9

Mozilla's advisory for Firefox 149 is the source of the severity rating. The vector in the NVD record reads CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

How to check if you're exposed

  1. Find your version. In Firefox open the menu, choose Help, then About Firefox. For Thunderbird use Help, then About Thunderbird.
  2. From a terminal, run firefox --version or thunderbird --version. On macOS the binary sits inside the app bundle, for example /Applications/Firefox.app/Contents/MacOS/firefox --version.
  3. On Debian or Ubuntu, apt list --installed 2>/dev/null | grep -i -E 'firefox|thunderbird' shows what the package manager installed. On Fedora or RHEL, use rpm -q firefox thunderbird.
  4. Compare the result with the fixed versions above. Anything older on the same branch is exposed to CVE-2026-4692.

Bundled copies are easy to miss. Kiosk images, test runners with a pinned Firefox, and container images can carry old builds, and a scan of the image catches those.

What to do now

  1. Update Firefox and Thunderbird on every managed device to the fixed version for the branch you run.
  2. Restart the browser after the update. Mozilla's updater only protects you once the new build is running.
  3. Update images and CI runners that pin a Firefox version, such as browser test containers.
  4. Where you cannot update today, limit who can browse untrusted sites from the affected machine and plan the update for the next change window.
  5. Record the new version in your inventory so the next review takes minutes.

Why it matters

The record maps this to CWE-653, which covers improper isolation or compartmentalization, meaning a boundary meant to contain code can be crossed. The affected component is Responsive Design Mode. Mozilla's advisory lists the entry as high impact and gives no further technical detail, which is normal while most users are still updating.

A sandbox escape matters because Firefox runs web content in restricted processes on purpose. A bug that lets code leave that box turns a contained problem into one on the whole machine. The NVD vector shows Scope Changed, which is how CVSS records exactly that kind of boundary crossing, and it produces the top score of 10.0. The record's KEV flag is false and the advisory does not report exploitation.

Quick check

Is CVE-2026-4692 exploited in the wild?

The record's KEV flag is false, and the Mozilla advisory I read does not say it is exploited. That can change, so keep watching the advisory and update promptly.

Which version fixes CVE-2026-4692 on ESR?

The record lists Firefox ESR 115.34, Firefox ESR 140.9. If you run a different ESR line, read the Mozilla advisory for it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.