MEDIUM 4.7

CVE-2026-12313: Firefox & Thunderbird Sandbox Escape and Information Disclosure

A vulnerability in Firefox and Thunderbird's process sandboxing mechanism allows an attacker to leak sensitive information and potentially escape the sandbox through a crafted webpage or message. The attack requires user interaction (such as visiting a malicious site or opening a specially prepared message) and affects your system's security boundary—the sandbox that isolates the browser process from the rest of your computer. Mozilla has patched this in Firefox 152, Firefox ESR 140.12, Thunderbird 152, and Thunderbird 140.12.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.7 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Weaknesses (CWE)
CWE-269
Affected products
4 configuration(s)
Published / Modified
2026-06-16 / 2026-06-17

NVD description (verbatim)

Information disclosure, sandbox escape in the Security: Process Sandboxing component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, Thunderbird 152, and Thunderbird 140.12.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12313 is an information disclosure and sandbox escape vulnerability in the Security: Process Sandboxing component affecting Mozilla Firefox and Thunderbird. The vulnerability is rooted in CWE-269 (Improper Access Control), allowing attackers to bypass sandbox restrictions and read memory outside the intended isolated process. The attack vector is network-based with low complexity; user interaction is required to trigger the vulnerability. The attack crosses trust boundaries (CVSS parameter S:C), resulting in the disclosure of confidential information with no integrity or availability impact. The CVSS 3.1 score of 4.7 reflects a medium-severity issue with limited but meaningful exposure potential.

Business impact

While the vulnerability cannot directly destroy or modify data, the information disclosure capability poses a compliance and data-protection risk. An attacker could extract sensitive data—browser session tokens, cached credentials, or user data—from a compromised browser process. For organizations subject to data-breach notification requirements, successful exploitation could trigger disclosure obligations. The sandbox escape aspect is particularly concerning because it weakens the isolation layer designed to contain browser-based attacks, potentially enabling follow-on attacks that target the host system. Remediation is straightforward via patching, limiting business disruption.

Affected systems

Firefox (all versions prior to 152), Firefox ESR (all versions prior to 140.12), Thunderbird (all versions prior to 152), and Thunderbird ESR (all versions prior to 140.12) are affected. Organizations relying on Firefox or Thunderbird for email, web browsing, or as embedded browser components should verify their deployed versions and apply updates. Users on automatic update tracks will receive patches automatically; managed deployments should validate patch rollout.

Exploitability

Exploitation requires crafting a malicious webpage or email message and convincing a user to visit or open it. There is no evidence of public or weaponized exploits at this time; the vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog. The low attack complexity and requirement for user interaction (but not special privileges) make this a moderate concern in environments with security-aware users. However, targeted attacks against high-value users or accounts are plausible, and the sandbox escape potential elevates the risk profile beyond typical information-disclosure bugs.

Remediation

Apply the following patches immediately: Firefox 152 or later, Firefox ESR 140.12 or later, Thunderbird 152 or later, or Thunderbird ESR 140.12 or later. Verify patch deployment across managed endpoints. For users on automatic updates, confirm that systems have checked for and installed updates post-2026-06-16. No workarounds are available other than avoiding untrusted websites and email content until patched.

Patch guidance

Deploy Firefox 152+ and Firefox ESR 140.12+ to all Firefox-dependent systems. For Thunderbird users, update to version 152 or ESR 140.12+. If you manage a fleet, prioritize systems used by high-risk users (executives, developers, system administrators) or those exposed to external email. Verify patch success by checking Help > About Firefox (or Help > About Thunderbird) to confirm the installed version matches or exceeds the patched release. Test in a staging environment if your organization requires change control; Mozilla's update process is stable and poses minimal regression risk.

Detection guidance

Monitor process execution and sandbox-related system calls for anomalies on systems running vulnerable Firefox or Thunderbird versions. Endpoint detection and response (EDR) tools should flag unsigned or suspicious code attempting to read process memory or escape sandbox boundaries. Web traffic and email logs may show indicators of malicious content delivery, though the attack itself occurs client-side. Implement network-based controls to restrict access to known phishing or watering-hole domains. Post-patching, confirm that Firefox/Thunderbird processes operate with expected privilege levels and sandbox isolation remains intact.

Why prioritize this

Medium CVSS score (4.7) and lack of KEV listing suggest this is not a critical emergency, but the sandbox-escape component and cross-boundary impact warrant prompt attention within a normal patching cycle. Organizations with high email or web dependency should prioritize this within 1–2 weeks; others can incorporate it into routine monthly updates. The lack of public exploits provides a reasonable window to patch before attackers can reliably weaponize the vulnerability.

Risk score, explained

The CVSS 3.1 base score of 4.7 (MEDIUM) reflects a network-accessible vulnerability with low attack complexity and user interaction required (AV:N/AC:L/UI:R). The confidentiality impact is low (C:L) with no integrity or availability loss (I:N/A:N), and the scope is changed (S:C), meaning the vulnerability can affect resources beyond the vulnerable component. This scoring appropriately captures that while data disclosure is limited, the sandbox escape nature and cross-trust-boundary implications elevate concern beyond a simple low-impact information leak. Organizations should not deprioritize this as merely 'low risk'—the medium rating is well-justified.

Frequently asked questions

Could an attacker fully compromise my computer through this vulnerability?

Not directly. The vulnerability discloses information and escapes the browser sandbox, but it does not grant code execution on the host system or administrative privileges. However, disclosed information (such as session tokens or cached data) could enable secondary attacks. Patching eliminates this risk vector.

Do I need to patch Firefox ESR separately from standard Firefox?

Yes. Firefox ESR and Firefox Extended Support Releases are versioned separately. Verify whether you are running standard Firefox (auto-updates to latest) or ESR (slower update cadence). Apply the appropriate patch: Firefox 152+ for standard, Firefox ESR 140.12+ for ESR-managed deployments.

Is this vulnerability being actively exploited in the wild?

No. The vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog as of the publication date. There is no evidence of public or weaponized exploits. However, organizations should not rely on this as a reason to delay patching—responsible researchers and attackers often work in parallel timelines.

What should I tell users who ask about this vulnerability?

Inform them that Mozilla has patched a medium-severity vulnerability affecting Firefox and Thunderbird and that they should apply updates when prompted. No user action beyond accepting the update is required. If you manage endpoints, communicate that IT will ensure patching is completed within the organization's update window.

This analysis is based on vendor advisories and CVE data current as of 2026-06-17. CVSS scores, affected versions, and patch guidance are provided for informational purposes and should be verified against the official Mozilla Security Advisory and your organization's vulnerability management system. This document does not constitute legal or compliance advice. Organizations should conduct their own risk assessment and apply patches according to internal policies and risk tolerance. SEC.co makes no warranty regarding the completeness or accuracy of this information and shall not be liable for damages arising from reliance on it. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).