CVE-2026-117883
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: HTML Parser 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-03) ---
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 eliminate use-after-free conditions by updating the DOM HTML parser component or avoiding processing of untrusted HTML documents: upgrade to Firefox 159, Firefox ESR 115.44, Firefox ESR 153.6 (or the corresponding fixed Red Hat builds), which remediates object lifecycle management in the DOM HTML parser component to prevent use-after-free conditions during document parsing, closing crafted HTML document parsing. Until patched, this is a concern on Systems running affected Firefox installations where users access untrusted web links or load untrusted HTML content, so Avoid navigating to untrusted links and restrict opening arbitrary or untrusted HTML documents in the browser. As a compensating measure, Ensure ASLR is enabled to randomize memory layout and hinder reliable exploitation of the parser memory corruption, Deploy builds with Full RELRO and PIE to enforce read-only relocations and impede code reuse or pointer overwrites, and Keep SELinux in Enforcing mode to confine the browser process and contain post-exploitation actions. These controls limit blast radius and contain exploitation, but they do not fix the underlying DOM HTML parser 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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 8.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
