Multiple vulnerabilities have been discovered in Mozilla products, the most severe of which could allow for arbitrary code execution. 

• Mozilla Firefox is a web browser used to access the Internet.
• Mozilla Firefox ESR is a version of the web browser intended to be deployed in large organizations.
• Mozilla Thunderbird is an email client.
• Mozilla Thunderbird ESR is a version of the email client intended to be deployed in large organizations.

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

Multiple vulnerabilities have been discovered in Mozilla products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows: 

Tactic: Initial Access (TA0001): 

Technique: Drive-by Compromise (T1189): 

• Use-after-free in the DOM. (CVE-2026-6746)
• Use-after-free in the WebRTC component. (CVE-2026-6747)
• Uninitialized memory in the Audio/Video. (CVE-2026-6748)
• Information disclosure due to uninitialized memory in the Graphics. (CVE-2026-6749)
• Privilege escalation in the Graphics. (CVE-2026-6750)
• Uninitialized memory in the Audio/Video. (CVE-2026-6751)
• Incorrect boundary conditions in the WebRTC component. (CVE-2026-6752)
• Incorrect boundary conditions in the WebRTC component. (CVE-2026-6753)
• Use-after-free in the JavaScript Engine component. (CVE-2026-6754)
• Memory safety bugs fixed in Firefox 150 and Thunderbird 150. (CVE-2026-6784)
• Memory safety bugs fixed in Firefox ESR 115.35, Firefox ESR 140.10, Thunderbird ESR 140.10, Firefox 150 and Thunderbird 150. (CVE-2026-6785)
• Memory safety bugs fixed in Firefox ESR 140.10, Thunderbird ESR 140.10, Firefox 150 and Thunderbird 150. (CVE-2026-6786)

Additional lower severity vulnerabilities include:

• Invalid pointer in the JavaScript. (CVE-2026-6757)
• Use-after-free in the Widget. (CVE-2026-6759)
• Privilege escalation in the Networking component. (CVE-2026-6761)
• Spoofing issue in the DOM. (CVE-2026-6762)
• Mitigation bypass in the File Handling component. (CVE-2026-6763)
• Incorrect boundary conditions in the DOM. (CVE-2026-6764)
• Information disclosure in the Form Autofill component. (CVE-2026-6765)
• Incorrect boundary conditions in the Libraries component in NSS. (CVE-2026-6766, CVE-2026-6772)
• Other issue in the Libraries component in NSS. (CVE-2026-6767)
• Privilege escalation in the Debugger component. (CVE-2026-6769)
• Other issue in the Storage. (CVE-2026-6770)
• Mitigation bypass in the DOM. (CVE-2026-6771, CVE-2026-6755, CVE-2026-6774)
• Incorrect boundary conditions in the WebRTC. (CVE-2026-6776)
• Integer overflow in the Libraries component in NSS. (CVE-2026-2781)
• Mitigation bypass in Firefox for Android. (CVE-2026-6756)
• Use-after-free in the JavaScript. (CVE-2026-6758)
• Mitigation bypass in the Networking. (CVE-2026-6760, CVE-2026-6768)
• Denial-of-service due to integer overflow in the Graphics. (CVE-2026-6773)
• Incorrect boundary conditions in the WebRTC component. (CVE-2026-6775)
• Other issue in the Networking. (CVE-2026-6777)
• Invalid pointer in the Audio/Video. (CVE-2026-6778)
• Other issue in the JavaScript Engine component. (CVE-2026-6779)
• Denial-of-service in the Audio/Video. (CVE-2026-6780, CVE-2026-6781)
• Information disclosure in the IP Protection component. (CVE-2026-6782)
• Incorrect boundary conditions, integer overflow in the Audio/Video. (CVE-2026-6783)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

We recommend the following actions be taken:

• Apply appropriate updates provided by Mozilla to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
• Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
• Safeguard 9.1: Ensure Use of Only Fully Supported Browsers and Email Clients: Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.
• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
• Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
• Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
• Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
• Restrict use of certain websites, block downloads/attachments, block JavaScript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
• Safeguard 9.2: Use DNS Filtering Services: Use DNS filtering services on all enterprise assets to block access to known malicious domains.
• Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
• Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
• Block execution of code on a system through application control, and/or script blocking. (M1038: Execution Prevention)
• Safeguard 2.5: Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
• Safeguard 2.6: Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
• Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
• Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
• Safeguard 13.2: Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
• Safeguard 13.7: Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.
• Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources. Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. (M1017: User Training)
• Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.