CVE-2026-117900

Description

A flaw was found in Firefox and Thunderbird. The Mozilla Foundation's Security Advisory describes the following issue: Use-after-free in the DOM: Editor component

Statement

Red Hat Product Security rates the severity of this flaw as determined by the Mozilla Foundation Security Advisory.

Mitigation

--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to prevent the dereference or reuse of freed memory objects within the DOM Editor component during document editing and DOM manipulation: upgrade to Firefox 159, Firefox ESR 115.44, and Firefox ESR 153.6 (or the corresponding fixed Red Hat builds), which resolves the use-after-free condition in the DOM: Editor component during document editing and DOM manipulation, closing all 2 injection vectors (crafted web page triggering DOM editor manipulation, crafted HTML content in email or rich text editor). Until patched, this is a concern on Firefox and Thunderbird installations on all platforms processing untrusted web or rich text content, so restrict browsing untrusted websites and avoid opening or rendering untrusted HTML and rich text content in browser and email clients. As a compensating measure, randomize userland process address space using ASLR to hinder reliable code reuse or control-flow hijacking via dangling DOM objects, compile browser binaries with Full RELRO and PIE to enforce read-only relocations and position-independent execution, and run SELinux in enforcing mode to confine the browser process domain if arbitrary code execution occurs. These controls limit blast radius and contain exploitation, but they do not fix the underlying DOM Editor use-after-free defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A8.8
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.