Skip to main content

Mozilla Firefox EUVDEUVD-2026-88806

| CVE-2026-100828 CRITICAL
Protection Mechanism Failure (CWE-693)
2026-09-29 mozilla GHSA-hccq-gj23-w7rq
9.6
CVSS 3.1 · Vendor: mozilla
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to malicious page
  2. Delivery
    Deliver crafted content to Bookmarks & History component
  3. Exploit
    Bypass built-in security mitigation
  4. Execution
    Chain with content-process bug
  5. Impact
    Compromise browser session

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Requires an unpatched Firefox (before 157) or Firefox ESR (before 153.4) and that the victim actively loads attacker-controlled web content (UI:R) which exercises the Bookmarks & History component to defeat a built-in security mitigation. The practical limiting factor is that this is a mitigation BYPASS (CWE-693): defeating the protection alone provides little direct damage and realistically must be chained with a separate content-process vulnerability to achieve the rated C:H/I:H/A:H impact. No authentication is required (PR:N) but user interaction is mandatory.

Impact

Signals point to a low-urgency, defense-in-depth fix rather than an active emergency. The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6) was reported by Mozilla and reflects a worst-case chained outcome; however, CWE-693 (Protection Mechanism Failure) describes a MITIGATION BYPASS, which by nature weakens an existing security control rather than directly achieving full confidentiality/integrity/availability compromise on its own - so the C:H/I:H/A:H impact likely assumes chaining with a separate content-process bug and is arguably inflated for the standalone flaw. Corroborating lower-risk signals: EPSS is 0.15% (4th percentile), SSVC shows Exploitation=none and Automatable=no (though Technical Impact=total), and there is no CISA KEV listing and no public POC. The consistency of these signals suggests a high-CVSS-but-currently-low-real-risk issue: important to patch as part of routine browser updates, not a drop-everything emergency. UI:R is a genuine limiter - a victim must load attacker-controlled content.

Exploit ScenarioDerived

An attacker lures a Firefox user to a malicious or compromised web page that exercises the Bookmarks & History component to bypass a built-in browser security mitigation, neutralizing a defense that would normally blunt a second memory-safety or content-process bug. On its own the bypass yields limited direct impact; chained with another content-process vulnerability it could contribute to broader compromise. No public exploit identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Mitigation bypass in Mozilla Firefox's Bookmarks & History component lets attacker-controlled web content defeat a built-in browser security protection, weakening the defenses that normally contain malicious pages. The issue affects Firefox builds prior to 157 and Firefox ESR builds prior to 153.4, is reachable without authentication (PR:N) but requires the victim to load attacker-supplied content (UI:R), and is confirmed fixed by the vendor in Firefox 157 and Firefox ESR 153.4. Independent assessment rates the real-world consequence as limited (C:L/I:L/A:N) because bypassing the protection alone yields little damage and must be chained with a separate content-process vulnerability to reach the headline CVSS 9.6 impact; EPSS is 0.15% (4th percentile), there is no KEV listing, and no public exploit identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade to Firefox 157 or Firefox ESR 153.4, both of which contain the fix per Mozilla's advisories (https://www.mozilla.org/security/advisories/mfsa2026-100/, https://www.mozilla.org/security/advisories/mfsa2026-97/, https://www.mozilla.org/security/advisories/mfsa2026-101/, https://www.mozilla.org/security/advisories/mfsa2026-103/). Because the flaw is a mitigation bypass rather than a directly exploitable primitive, there is no clean configuration switch that removes it on unpatched builds; the realistic interim measures are to enforce browser updates through enterprise policy or managed deployment, restrict browsing to trusted sites via policy/EAS or URL filtering (reduces exposure to attacker-hosted content but is impractical for general web use and degrades usability), and keep content-process protections otherwise current so the bypass cannot be chained with a second flaw to reach total impact. Accelerating ESR-to-153.4 migration is the highest-value action given that ESR instances are typically the slowest to update; the low EPSS (0.15%), absence of KEV listing, and SSVC Exploitation: none support treating this as a defense-in-depth fix rather than an emergency, though patching should not be deferred indefinitely.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a Protection Mechanism Failure (CWE-693) in the Bookmarks & History component of the Gecko-based Firefox browser. Rather than a memory-safety bug, it involves a security control that Firefox relies on to bound what web content can do once it is loaded alongside or through bookmarks/history functionality; the bypass lets content escape or negate that control. Mozilla's own CVSS 3.1 vector scores it 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), reflecting changed scope and worst-case confidentiality/integrity/availability if the bypass is leveraged, whereas the independent assessment scores the same vector shape at C:L/I:L/A:N - the difference being that defeating a mitigation is only a stepping stone, not a self-contained compromise. CPE data (cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*) confirms the affected package is Firefox itself across all versions prior to the fixed releases. No authentication is required to trigger the flaw, but user interaction is mandatory since the victim must actively load attacker-controlled web content that exercises the Bookmarks & History component.

Know when Firefox gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mozilla) PRIMARY 9.6 CRITICAL
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
vuln.today AI 6.1 MEDIUM

Remote drive-by needs victim page load (UI:R, PR:N); as a standalone CWE-693 mitigation bypass direct impact is limited (C:L/I:L), with S:C reflecting the weakened cross-boundary defense.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (mozilla).

CVSS VectorVendor: mozilla

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 01, 2026 - 16:22 NVD
9.6 (None) 9.6 (CRITICAL)
CVE Published
Sep 29, 2026 - 12:36 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 29, 2026 - 12:36 cve.org
CRITICAL 9.6

DescriptionCVE.org

Mitigation bypass in the Bookmarks & History component. This vulnerability was fixed in Firefox ESR 153.4 and Firefox 157.

Executive ViewAI

Why It Matters

A critical-severity mitigation bypass in Mozilla Firefox's Bookmarks & History component affects Firefox builds prior to 157 and Firefox ESR builds prior to 153.4, weakening one of the built-in protections that normally contains hostile web content on a browser installed across most corporate endpoints. On its own the flaw yields only limited damage - meaningful impact requires chaining it with a separate content-process vulnerability - and there is no confirmed exploitation or public exploit code at this time. Leadership should track it because Firefox's footprint makes the affected population large, while recognising that current real-world risk is contained rather than imminent.

Business Impact: Medium
Compensating Controls

Apply vendor patch (Firefox 157 / Firefox ESR 153.4). Where immediate upgrade is not possible, treat untrusted web content and links as higher risk on affected builds, restrict or isolate high-risk browsing to an alternate or sandboxed browser, and rely on endpoint detection and content-process isolation controls until the upgrade completes.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
High
Firefox is a major cross-platform browser, including enterprise ESR deployments
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)CVE.org

cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*
CVE-2013-0758 CRITICAL POC
9.3 Jan 13

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb

CVE-2013-0753 CRITICAL POC
9.3 Jan 13

Use-after-free vulnerability in the serializeToStream implementation in the XMLSerializer component in Mozilla Firefox b

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2013-1710 CRITICAL POC
10.0 Aug 07

The crypto.generateCRMFRequest function in Mozilla Firefox before 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird befo

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2014-1511 CRITICAL POC
9.8 Mar 19

Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and SeaMonkey before 2.25 allow remo

CVE-2016-1960 HIGH POC
8.8 Mar 13

Integer underflow in the nsHtml5TreeBuilder class in the HTML5 string parser in Mozilla Firefox before 45.0 and Firefox

CVE-2015-0816 MEDIUM POC
5.0 Apr 01

Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 do not properly restrict resource

CVE-2015-0802 MEDIUM POC
5.0 Apr 01

Mozilla Firefox before 37.0 relies on docshell type information instead of page principal information for Window.webidl

CVE-2013-2566 MEDIUM POC
5.9 Mar 15

The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy