CVE-2026-12316: Mozilla Firefox · CWE-693
Affects Mozilla FirefoxSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · patch available : patch Mozilla Firefox as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mozilla Firefox | Affected
| Fixed in
|
AI-suggested
Mozilla has released an official fix for this vulnerability in Firefox version 152. Users and administrators should update affected Firefox installations to version 152 or later to remediate this issue. Since this is not a cloud service, local patching is required. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-12316 is a mitigation bypass vulnerability in the DOM security component of Mozilla Firefox. This vulnerability, along with numerous other critical and moderate security issues including memory safety bugs, sandbox escapes, and use-after-free flaws, were fixed in Firefox version 152. The vulnerability affects Firefox versions prior to 152. The CVSS score is 9.1, indicating critical severity with high impact on confidentiality and integrity. No known exploits in the wild have been reported. The vendor advisory confirms that the issue is fixed in Firefox 152.