ALSA-2026:89757 (CVE-2026-109704)
Vulnerability from osv_almalinux – Published: 2026-10-26 00:00 – Updated: 2026-10-31 12:54 – Source websiteMozilla Firefox is an open-source web browser, designed for standards compliance, performance, and portability.
Security Fix(es):
- libexpat: denial of service via crafted XML input (CVE-2026-45186)
- firefox: thunderbird: Privilege escalation in the Application Update component (CVE-2026-109704)
- firefox: Use-after-free in the XML component (CVE-2026-109718)
- firefox: Information disclosure in the PDF Viewer component (CVE-2026-109742)
- firefox: Incorrect boundary conditions in the JavaScript Engine component (CVE-2026-109715)
- firefox: firefox: Sandbox escape via incorrect boundary conditions in Win32 widget (CVE-2026-109740)
- firefox: Use-after-free in the Storage: IndexedDB component (CVE-2026-109706)
- firefox: Use-after-free in the Crash Reporting component (CVE-2026-109713)
- firefox: Use-after-free in the DOM: Core & HTML component (CVE-2026-109724)
- firefox: Sandbox escape due to uninitialized memory in the DOM: Web Serial component (CVE-2026-109745)
- firefox: Mitigation bypass in the File Handling component (CVE-2026-109782)
- firefox: Information disclosure, privilege escalation in the Security: Process Sandboxing component (CVE-2026-109709)
- firefox: Sandbox escape, site isolation issue due to incorrect boundary conditions, use-after-free in the Networking component (CVE-2026-109705)
- firefox: Use-after-free in the Audio/Video: Playback component (CVE-2026-109738)
- firefox: Sandbox escape due to race condition in the Networking component (CVE-2026-109757)
- firefox: Use-after-free in the Storage: Bucket File System component (CVE-2026-109741)
- firefox: Use-after-free in the JavaScript Engine: JIT component (CVE-2026-109729)
- firefox: Other issue in the DOM: File component (CVE-2026-109744)
- firefox: Incorrect boundary conditions in the JavaScript Engine component (CVE-2026-109716)
- firefox: Race condition, use-after-free in the Graphics: CanvasWebGL component (CVE-2026-109719)
- firefox: Incorrect boundary conditions in the Layout component (CVE-2026-109753)
- firefox: Integer overflow in the Layout: Text and Fonts component (CVE-2026-109723)
- firefox: Privilege escalation in the DOM: Navigation component (CVE-2026-109756)
- firefox: JIT miscompilation in the JavaScript Engine: JIT component (CVE-2026-109733)
- firefox: Mitigation bypass in the File Handling component (CVE-2026-109763)
- firefox: Sandbox escape due to incorrect boundary conditions in the Networking component (CVE-2026-109708)
- firefox: Use-after-free in the DOM: Bindings (WebIDL) component (CVE-2026-109717)
- firefox: Use-after-free in the DOM: Workers component (CVE-2026-109752)
- firefox: Sandbox escape due to use-after-free in the Networking component (CVE-2026-109707)
- firefox: Mitigation bypass in the Networking: HTTP component (CVE-2026-109760)
- firefox: JIT miscompilation in the JavaScript: WebAssembly component (CVE-2026-109720)
- firefox: Use-after-free in the SVG component (CVE-2026-109726)
- firefox: Integer overflow in the Graphics component (CVE-2026-109730)
- firefox: Use-after-free in the Audio/Video component (CVE-2026-109727)
- firefox: Mitigation bypass in the Enterprise Policies component (CVE-2026-109737)
- firefox: Use-after-free in the DOM: Streams component (CVE-2026-109732)
- firefox: Site isolation issue in the Networking component (CVE-2026-109759)
- firefox: Incorrect boundary conditions in the SVG component (CVE-2026-109762)
- firefox: Incorrect boundary conditions in the DOM: Editor component (CVE-2026-109754)
- firefox: Information disclosure in the Networking component (CVE-2026-109751)
- firefox: Use-after-free in the DOM: Core & HTML component (CVE-2026-109725)
- firefox: Sandbox escape due to uninitialized memory in the Graphics component (CVE-2026-109712)
- firefox: Use-after-free in the Graphics: Canvas2D component (CVE-2026-109711)
- firefox: Frame poisoning in the Layout component (CVE-2026-109736)
- firefox: JIT miscompilation in the JavaScript Engine: JIT component (CVE-2026-109722)
- firefox: Use-after-free in the DOM: Animation component (CVE-2026-109728)
- firefox: Incorrect boundary conditions in the JavaScript Engine: JIT component (CVE-2026-109721)
- firefox: Privilege escalation in the Panning and Zooming component (CVE-2026-109743)
Bug Fix(es) and Enhancement(s):
- Firefox ESR 153 rebase [rhel-9.8.z] (JIRA:RHEL-175155)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "firefox"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "153.5.0-1.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "firefox-x11"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "153.5.0-1.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "Mozilla Firefox is an open-source web browser, designed for standards compliance, performance, and portability. \n\nSecurity Fix(es): \n\n * libexpat: denial of service via crafted XML input (CVE-2026-45186)\n * firefox: thunderbird: Privilege escalation in the Application Update component (CVE-2026-109704)\n * firefox: Use-after-free in the XML component (CVE-2026-109718)\n * firefox: Information disclosure in the PDF Viewer component (CVE-2026-109742)\n * firefox: Incorrect boundary conditions in the JavaScript Engine component (CVE-2026-109715)\n * firefox: firefox: Sandbox escape via incorrect boundary conditions in Win32 widget (CVE-2026-109740)\n * firefox: Use-after-free in the Storage: IndexedDB component (CVE-2026-109706)\n * firefox: Use-after-free in the Crash Reporting component (CVE-2026-109713)\n * firefox: Use-after-free in the DOM: Core \u0026 HTML component (CVE-2026-109724)\n * firefox: Sandbox escape due to uninitialized memory in the DOM: Web Serial component (CVE-2026-109745)\n * firefox: Mitigation bypass in the File Handling component (CVE-2026-109782)\n * firefox: Information disclosure, privilege escalation in the Security: Process Sandboxing component (CVE-2026-109709)\n * firefox: Sandbox escape, site isolation issue due to incorrect boundary conditions, use-after-free in the Networking component (CVE-2026-109705)\n * firefox: Use-after-free in the Audio/Video: Playback component (CVE-2026-109738)\n * firefox: Sandbox escape due to race condition in the Networking component (CVE-2026-109757)\n * firefox: Use-after-free in the Storage: Bucket File System component (CVE-2026-109741)\n * firefox: Use-after-free in the JavaScript Engine: JIT component (CVE-2026-109729)\n * firefox: Other issue in the DOM: File component (CVE-2026-109744)\n * firefox: Incorrect boundary conditions in the JavaScript Engine component (CVE-2026-109716)\n * firefox: Race condition, use-after-free in the Graphics: CanvasWebGL component (CVE-2026-109719)\n * firefox: Incorrect boundary conditions in the Layout component (CVE-2026-109753)\n * firefox: Integer overflow in the Layout: Text and Fonts component (CVE-2026-109723)\n * firefox: Privilege escalation in the DOM: Navigation component (CVE-2026-109756)\n * firefox: JIT miscompilation in the JavaScript Engine: JIT component (CVE-2026-109733)\n * firefox: Mitigation bypass in the File Handling component (CVE-2026-109763)\n * firefox: Sandbox escape due to incorrect boundary conditions in the Networking component (CVE-2026-109708)\n * firefox: Use-after-free in the DOM: Bindings (WebIDL) component (CVE-2026-109717)\n * firefox: Use-after-free in the DOM: Workers component (CVE-2026-109752)\n * firefox: Sandbox escape due to use-after-free in the Networking component (CVE-2026-109707)\n * firefox: Mitigation bypass in the Networking: HTTP component (CVE-2026-109760)\n * firefox: JIT miscompilation in the JavaScript: WebAssembly component (CVE-2026-109720)\n * firefox: Use-after-free in the SVG component (CVE-2026-109726)\n * firefox: Integer overflow in the Graphics component (CVE-2026-109730)\n * firefox: Use-after-free in the Audio/Video component (CVE-2026-109727)\n * firefox: Mitigation bypass in the Enterprise Policies component (CVE-2026-109737)\n * firefox: Use-after-free in the DOM: Streams component (CVE-2026-109732)\n * firefox: Site isolation issue in the Networking component (CVE-2026-109759)\n * firefox: Incorrect boundary conditions in the SVG component (CVE-2026-109762)\n * firefox: Incorrect boundary conditions in the DOM: Editor component (CVE-2026-109754)\n * firefox: Information disclosure in the Networking component (CVE-2026-109751)\n * firefox: Use-after-free in the DOM: Core \u0026 HTML component (CVE-2026-109725)\n * firefox: Sandbox escape due to uninitialized memory in the Graphics component (CVE-2026-109712)\n * firefox: Use-after-free in the Graphics: Canvas2D component (CVE-2026-109711)\n * firefox: Frame poisoning in the Layout component (CVE-2026-109736)\n * firefox: JIT miscompilation in the JavaScript Engine: JIT component (CVE-2026-109722)\n * firefox: Use-after-free in the DOM: Animation component (CVE-2026-109728)\n * firefox: Incorrect boundary conditions in the JavaScript Engine: JIT component (CVE-2026-109721)\n * firefox: Privilege escalation in the Panning and Zooming component (CVE-2026-109743)\n\n\nBug Fix(es) and Enhancement(s): \n\n * Firefox ESR 153 rebase [rhel-9.8.z] (JIRA:RHEL-175155)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n",
"id": "ALSA-2026:89757",
"modified": "2026-10-31T12:54:27Z",
"published": "2026-10-26T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2026:89757"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109704"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109705"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109706"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109707"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109708"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109709"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109711"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109712"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109713"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109715"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109716"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109717"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109718"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109719"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109720"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109721"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109722"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109723"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109724"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109725"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109726"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109727"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109728"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109729"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109730"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109732"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109733"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109736"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109737"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109738"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109740"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109741"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109742"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109743"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109744"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109745"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109751"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109752"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109753"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109754"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109756"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109757"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109759"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109760"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109762"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109763"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-109782"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-45186"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2468575"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550397"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550404"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550405"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550413"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550419"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550420"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550424"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550433"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550438"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550446"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550451"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2550455"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/9/ALSA-2026-89757.html"
}
],
"related": [
"CVE-2026-109704",
"CVE-2026-109705",
"CVE-2026-109706",
"CVE-2026-109707",
"CVE-2026-109708",
"CVE-2026-109709",
"CVE-2026-109711",
"CVE-2026-109712",
"CVE-2026-109713",
"CVE-2026-109715",
"CVE-2026-109716",
"CVE-2026-109717",
"CVE-2026-109718",
"CVE-2026-109719",
"CVE-2026-109720",
"CVE-2026-109721",
"CVE-2026-109722",
"CVE-2026-109723",
"CVE-2026-109724",
"CVE-2026-109725",
"CVE-2026-109726",
"CVE-2026-109727",
"CVE-2026-109728",
"CVE-2026-109729",
"CVE-2026-109730",
"CVE-2026-109732",
"CVE-2026-109733",
"CVE-2026-109736",
"CVE-2026-109737",
"CVE-2026-109738",
"CVE-2026-109740",
"CVE-2026-109741",
"CVE-2026-109742",
"CVE-2026-109743",
"CVE-2026-109744",
"CVE-2026-109745",
"CVE-2026-109751",
"CVE-2026-109752",
"CVE-2026-109753",
"CVE-2026-109754",
"CVE-2026-109756",
"CVE-2026-109757",
"CVE-2026-109759",
"CVE-2026-109760",
"CVE-2026-109762",
"CVE-2026-109763",
"CVE-2026-109782",
"CVE-2026-45186"
],
"schema_version": "1.7.0",
"summary": "Important: firefox security, bug fix, and enhancement update",
"upstream": [
"CVE-2026-109704",
"CVE-2026-109705",
"CVE-2026-109706",
"CVE-2026-109707",
"CVE-2026-109708",
"CVE-2026-109709",
"CVE-2026-109711",
"CVE-2026-109712",
"CVE-2026-109713",
"CVE-2026-109715",
"CVE-2026-109716",
"CVE-2026-109717",
"CVE-2026-109718",
"CVE-2026-109719",
"CVE-2026-109720",
"CVE-2026-109721",
"CVE-2026-109722",
"CVE-2026-109723",
"CVE-2026-109724",
"CVE-2026-109725",
"CVE-2026-109726",
"CVE-2026-109727",
"CVE-2026-109728",
"CVE-2026-109729",
"CVE-2026-109730",
"CVE-2026-109732",
"CVE-2026-109733",
"CVE-2026-109736",
"CVE-2026-109737",
"CVE-2026-109738",
"CVE-2026-109740",
"CVE-2026-109741",
"CVE-2026-109742",
"CVE-2026-109743",
"CVE-2026-109744",
"CVE-2026-109745",
"CVE-2026-109751",
"CVE-2026-109752",
"CVE-2026-109753",
"CVE-2026-109754",
"CVE-2026-109756",
"CVE-2026-109757",
"CVE-2026-109759",
"CVE-2026-109760",
"CVE-2026-109762",
"CVE-2026-109763",
"CVE-2026-109782",
"CVE-2026-45186"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.