CVE-2026-2790 Overview
CVE-2026-2790 is a same-origin policy bypass vulnerability affecting the Networking: JAR component in Mozilla Firefox and Thunderbird. The same-origin policy (SOP) is a fundamental browser security mechanism that restricts how documents or scripts from one origin can interact with resources from another origin. This bypass allows attackers to circumvent these critical security boundaries, potentially enabling cross-origin data theft, session hijacking, and other severe attacks through maliciously crafted JAR file handling.
Critical Impact
This same-origin policy bypass vulnerability allows network-based attackers to circumvent fundamental browser security boundaries without user interaction, potentially enabling unauthorized access to sensitive cross-origin data and complete compromise of user sessions.
Affected Products
- Mozilla Firefox < 148
- Mozilla Firefox ESR < 140.8
- Mozilla Thunderbird < 148
- Mozilla Thunderbird ESR < 140.8
Discovery Timeline
- 2026-02-24 - CVE-2026-2790 published to NVD
- 2026-02-26 - Last updated in NVD database
Technical Details for CVE-2026-2790
Vulnerability Analysis
This vulnerability resides in the Networking: JAR component of Mozilla products. JAR (Java Archive) files are essentially ZIP archives that can contain web resources, and browsers have historically supported the jar: URI scheme to access content within these archives. The same-origin policy bypass occurs when the browser fails to properly validate or enforce origin restrictions when handling JAR file content.
When processing JAR URIs, the affected versions of Firefox and Thunderbird do not correctly enforce same-origin restrictions, allowing malicious content to access resources from different origins. This breaks the fundamental security boundary that prevents websites from reading data from other sites, potentially exposing sensitive information such as authentication tokens, personal data, or session cookies from other origins.
The vulnerability is classified under CWE-346 (Origin Validation Error), which describes failures to properly verify that the source of data or communication is valid. In this case, the JAR networking component fails to maintain proper origin isolation, allowing cross-origin access that should be prohibited.
Root Cause
The root cause stems from improper origin validation in the Networking: JAR component. When the browser processes requests involving JAR URIs, the origin checking mechanism fails to properly associate the contained resources with their correct origin, or incorrectly inherits origins from the enclosing document. This implementation flaw allows scripts or content loaded from a JAR file to bypass same-origin restrictions that would normally prevent cross-origin data access.
Attack Vector
This vulnerability can be exploited via network-based attacks with no privileges required and no user interaction necessary. An attacker can exploit this vulnerability by:
- Hosting a malicious JAR file on an attacker-controlled server
- Enticing a victim to visit a webpage that references or loads the malicious JAR content
- The JAR content can then bypass same-origin restrictions to read data from other origins
- Sensitive data from other websites the user has access to can be exfiltrated to the attacker
The attack does not require any specific user interaction beyond normal browsing activity, making it particularly dangerous. The network attack vector combined with low complexity and no authentication requirements means this vulnerability could be exploited at scale against any user running vulnerable versions of Firefox or Thunderbird.
Detection Methods for CVE-2026-2790
Indicators of Compromise
- Unusual network requests to jar: URIs from untrusted sources or unexpected domains
- JavaScript attempting to access cross-origin resources through JAR protocol handling
- Unexpected outbound data exfiltration following access to pages containing embedded JAR references
- Browser logs showing JAR-related resource loads from suspicious external sources
Detection Strategies
- Monitor for jar: URI scheme usage in network traffic, particularly from external untrusted sources
- Implement browser extension or proxy-based detection for cross-origin requests following JAR content loading
- Deploy network security monitoring to detect unusual patterns of cross-site data access
- Review web application firewall logs for attempts to serve malicious JAR content
Monitoring Recommendations
- Enable detailed browser logging to capture JAR URI processing events and origin violations
- Implement Content Security Policy (CSP) reporting to detect policy violation attempts
- Monitor endpoint detection systems for browsers exhibiting abnormal cross-origin behavior
- Track security advisories from Mozilla for updated indicators related to this vulnerability
How to Mitigate CVE-2026-2790
Immediate Actions Required
- Update Mozilla Firefox to version 148 or later immediately
- Update Mozilla Firefox ESR to version 140.8 or later
- Update Mozilla Thunderbird to version 148 or later
- Update Mozilla Thunderbird ESR to version 140.8 or later
- Verify all managed endpoints have received the security updates
Patch Information
Mozilla has released security patches addressing this vulnerability across all affected product lines. The fixes are documented in multiple Mozilla Security Advisories:
- Mozilla Security Advisory MFSA-2026-13
- Mozilla Security Advisory MFSA-2026-15
- Mozilla Security Advisory MFSA-2026-16
- Mozilla Security Advisory MFSA-2026-17
Additional technical details are available in Mozilla Bug Report #2008426.
Workarounds
- Restrict browsing to trusted sites only until patches can be applied
- Consider using alternative browsers temporarily if immediate patching is not possible
- Implement network-level blocking of jar: URI requests from untrusted external sources
- Deploy browser isolation solutions to contain potential exploitation attempts
# Firefox update verification (Linux/macOS)
firefox --version
# Ensure output shows version 148 or higher (or 140.8+ for ESR)
# Thunderbird update verification
thunderbird --version
# Ensure output shows version 148 or higher (or 140.8+ for ESR)
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

