Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted font/text layout data
-
ExploitTrigger integer overflow in layout engine
-
ExecutionCorrupt memory / leak limited data
-
ImpactPartial confidentiality and integrity impact
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to use an affected Firefox build (prior to Firefox 158 or ESR 153.5) and to load attacker-controlled web content that exercises the Layout: Text and Fonts code path with malformed text/font data that triggers the CWE-190 integer overflow. The principal limiting factor is mandatory user interaction (UI:R) - the user must navigate to or render the malicious page; there is no authentication requirement (PR:N). No special non-default Firefox configuration is indicated in the description, so default installations rendering web content are in scope, but the attacker cannot act purely remotely without the victim loading the content, and impact is bounded (no availability impact, only limited confidentiality/integrity). |
| Impact | Signals are consistent and point to a moderate, low-priority issue despite Firefox's massive install base. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N, base 5.4) describes a network-reachable, low-complexity, unauthenticated flaw that nonetheless requires user interaction (UI:R) - i.e. the victim must load attacker-controlled web content - and yields only partial confidentiality and integrity impact with no availability impact. EPSS is low at 0.15% (4th percentile), and there is no CISA KEV listing and no public exploit identified at time of analysis, so there is no evidence of exploitation pressure. The Integer Overflow/Buffer Overflow tags and CWE-190 in the Layout text/font engine raise the theoretical specter of memory corruption, but the vendor-assigned C:L/I:L/A:N impact and absence of an RCE/high-availability rating suggest the overflow does not translate into a reliably weaponizable code-execution primitive here. No SSVC decision data was provided in the input, so automatable/technical-impact fields could not be factored in. Net: a real but not urgent browser memory-safety bug - patch in normal cycle rather than emergency. |
| Exploit ScenarioDerived | An attacker crafts a malicious web page containing specially constructed text or font layout data that triggers the integer overflow in Firefox's Layout: Text and Fonts component when the victim browses to the page. Because user interaction is required (UI:R), the victim must be lured to the attacker-controlled or compromised site; successful exploitation leaks limited in-process information or corrupts limited state (C:L/I:L). No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
An integer overflow (CWE-190) in Firefox's Layout: Text and Fonts component can be triggered when a user renders attacker-controlled web content containing malformed text or font data, potentially causing memory-safety corruption in the browser process. The vulnerability affects Firefox builds prior to version 158 and Firefox ESR builds prior to 153.5, is reachable without authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R), but requires the victim to load the crafted page, and its assessed impact is bounded to low confidentiality and integrity effects with no availability impact (score 5.4). Exploitation is not confirmed in the field: there is no CISA KEV listing and no public exploit identified at time of analysis, and the EPSS score of 0.15% (4th percentile) indicates a low predicted likelihood of exploitation activity.
RemediationAI
Vendor-released patch: Firefox 158 and Firefox ESR 153.5 - upgrade to at least those versions and follow the guidance in Mozilla advisories mfsa2026-106, mfsa2026-108, mfsa2026-109 and mfsa2026-110 (https://www.mozilla.org/security/advisories/mfsa2026-106/, https://www.mozilla.org/security/advisories/mfsa2026-108/, https://www.mozilla.org/security/advisories/mfsa2026-109/, https://www.mozilla.org/security/advisories/mfsa2026-110/); ESR channel operators should treat 153.5 as the minimum fixed build and prioritise the upgrade because long-lived ESR installs otherwise remain exposed for extended periods. Because no patch-free fix or vendor-documented workaround is listed, the practical compensating controls are exposure-reduction measures rather than fixes: disable downloadable web fonts in enterprise configuration (gfx.downloadable_fonts.enabled=false), which removes the font-processing surface that reaches the Layout: Text and Fonts path but visibly breaks typography on many sites, and enforce content filtering or disable JavaScript-dependent rich text rendering on high-risk browsing profiles, with the trade-off of degrading general browsing fidelity. Deploying exploit-mitigation hardening (browser process sandboxing, site isolation, OS-level mitigations) reduces the consequence of a successful overflow but does not prevent the trigger; because exploitation requires the victim to load attacker-controlled content, the most reliable near-term risk reduction is prompt patching plus restricting users from untrusted web content on unpatched hosts. Given the low EPSS score (0.15%, 4th percentile) and the absence of confirmed exploitation, this can be scheduled as a routine patch rather than an emergency change, prioritising internet-facing and high-value ESR endpoints first.
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 resides in the Gecko layout engine's text and font handling code path - specifically the subcomponent Mozilla labels 'Layout: Text and Fonts', which parses font tables, shapes glyph runs and computes text metrics. The root cause class is CWE-190 (Integer Overflow or Wraparound): an arithmetic operation on attacker-influenced size or offset values can wrap, producing an undersized allocation or an out-of-bounds index, which the associated tags characterise as a potential buffer overflow. Affected software is identified by the CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* and the tracking bug is Bugzilla 2074171; the underlying issue is the same class of memory-safety defect Mozilla has repeatedly fixed in font/text layout (e.g. table parsing and glyph metric calculations). The supplied CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) implies the overflow does not yield a directly demonstrable code-execution primitive or denial of service in the assessed scenario, consistent with a bounded out-of-bounds condition rather than a full sandbox escape or remote code execution.
Know when Mozilla 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
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Web content is network-delivered (AV:N) with no auth (PR:N) but requires the victim to render a malicious page (UI:R); vendor-rated limited memory impact gives C:L/I:L/A:N.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Integer overflow in the Layout: Text and Fonts component. This vulnerability was fixed in Firefox 158 and Firefox ESR 153.5.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Affected Products (CPE)CVE.org
The PDF reader in Mozilla Firefox before 39.0.3, Firefox ESR 38.x before 38.1.1, and Firefox OS before 2.2 allows remote
Mozilla Firefox before 22.0, Firefox ESR 17.x before 17.0.7, Thunderbird before 17.0.7, and Thunderbird ESR 17.x before
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
Use-after-free vulnerability in the serializeToStream implementation in the XMLSerializer component in Mozilla Firefox b
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
The crypto.generateCRMFRequest function in Mozilla Firefox before 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird befo
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and SeaMonkey before 2.25 allow remo
The Firefox sandbox in Adobe Flash Player before 10.3.183.67 and 11.x before 11.6.602.171 on Windows and Mac OS X, and b
EUVD-2026-98493
GHSA-94rc-qqr5-2gj6
NVD
CVE.org
EPSS
Exploit-DB