CVE-2026-4699
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect boundary conditions in the Layout: Text and Fonts component. This vulnerability was fixed in Firefox 149, Firefox ESR 115.34, Firefox ESR 140.9, Thunderbird 149, and Thunderbird 140.9.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMemory safety vulnerability in Mozilla Firefox and Thunderbird's Layout: Text and Fonts component caused by incorrect boundary conditions during text and font processing. This could allow memory corruption leading to potential code execution or crash conditions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 115.34.0< 149.0>= 128.0, < 140.9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Firefox versionIn Firefox, go to Menu > Help > About Firefox (or navigate to about:support). The version number is displayed on this page.Affected if The installed version is < 115.34.0 OR (>= 128.0 AND < 140.9.0) OR < 149.0 (version falls within any of the vulnerable ranges)
-
Determine installed Thunderbird versionIn Thunderbird, go to Menu > Help > About Thunderbird (or navigate to about:support). The version number is displayed on this page.Affected if The installed version is < 115.34.0 OR (>= 128.0 AND < 140.9.0) OR < 149.0 (version falls within any of the vulnerable ranges)
-
Verify Text and Fonts processing is activeThis vulnerability affects the Layout: Text and Fonts component. The flaw is triggered during text and font rendering operations in the browser or email client. Any page displaying text or any email being viewed would exercise this code path.Affected if The product is actively used to render web content (Firefox) or view emails with text/fonts (Thunderbird), meaning the affected code path is being exercised
You are affected if your Firefox or Thunderbird version is less than 115.34.0, or between 128.0 and 140.8.x, or less than 149.0 (checking against the specific version ranges provided), and you actively use the browser or email client to render content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped115.34.0140.9.0149.0
Update affected Mozilla products (Firefox and Thunderbird) to the patched versions: Firefox 149/ESR 115.34/ESR 140.9 or later, Thunderbird 149/140.9 or later.
Firefox 149 (or Firefox ESR 115.34 / Firefox ESR 140.9 for ESR users); Thunderbird 149 or Thunderbird 140.9
- Check the current Firefox version by navigating to Menu > Help > About Firefox (or entering 'about:support' in the address bar)
- If version is < 115.34.0, upgrade to Firefox 115.34.0 or later (or ESR 115.34)
- If version is >= 128.0 and < 140.9.0, upgrade to Firefox 140.9.0 or later (Firefox 149 is recommended)
- If version is >= 140.9.0 and < 149, upgrade to Firefox 149 or later
- For Thunderbird users: upgrade to Thunderbird 140.9 or Thunderbird 149 depending on current version
- After upgrade, verify the version by checking Menu > Help > About to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- bugzilla.mozilla.org
- www.mozilla.org
- www.mozilla.org
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- bugzilla.redhat.com
- security.access.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4699 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data