CVE-2026-92239

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A maliciously constructed IMAP line could cause an out-of-bounds buffer read. This vulnerability was fixed in Thunderbird 156, Thunderbird 140.16, and Thunderbird 153.3.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 15, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available.
generic

Security Vulnerabilities fixed in Thunderbird 153.3 — Mozilla

https://www.mozilla.org/security/advisories/mfsa2026-96/
generic

Security Vulnerabilities fixed in Thunderbird 140.16 — Mozilla

https://www.mozilla.org/security/advisories/mfsa2026-95/
generic

Security Vulnerabilities fixed in Thunderbird 156 — Mozilla

https://www.mozilla.org/security/advisories/mfsa2026-94/
generic

Access Denied

https://bugzilla.mozilla.org/show_bug.cgi?id=2060488

Vendor Advisories for CVE-2026-92239(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatthunderbird-0:140.16.0-1.el8_102026-09-30redhat
redhatthunderbird-0:140.16.0-1.el10_22026-09-29redhat
redhatthunderbird-0:140.16.0-1.el9_82026-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
thunderbird1:102.11.0-1 ... 1:140.9.1esr-1~deb13u1 (229 versions)
  • every version up to 1:140.16.0esr-1~deb12u1: fixed in 1:140.16.0esr-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
thunderbird1:128.13.0esr-1 ... 1:140.9.1esr-1~deb13u1 (85 versions)
  • every version up to 1:140.16.0esr-1~deb13u1: fixed in 1:140.16.0esr-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
thunderbird1:128.13.0esr-1 ... 1:155.0.1-2 (99 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 43× in last 7d / 98× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 11:55 UTCVendor advisory
  2. 2026-10-05 11:55 UTCGHSA enrichment
  3. 2026-10-05 00:38 UTCEG score recompute
  4. 2026-10-05 00:38 UTCVendor advisory
  5. 2026-10-05 00:38 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 13:21 UTCVendor advisory
  8. 2026-10-04 13:21 UTCGHSA enrichment
  9. 2026-10-04 02:04 UTCVendor advisory
  10. 2026-10-04 02:04 UTCGHSA enrichment
  11. 2026-10-03 14:47 UTCEG score recompute
  12. 2026-10-03 14:47 UTCVendor advisory
  13. 2026-10-03 14:47 UTCGHSA enrichment
  14. 2026-10-03 03:21 UTCEG score recompute
  15. 2026-10-03 03:21 UTCVendor advisory
  16. 2026-10-03 03:21 UTCGHSA enrichment
  17. 2026-10-02 16:04 UTCVendor advisory
  18. 2026-10-02 16:04 UTCGHSA enrichment
  19. 2026-10-02 04:47 UTCEG score recompute
  20. 2026-10-02 04:47 UTCVendor advisory
  21. 2026-10-02 04:46 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 17:25 UTCVendor advisory
  24. 2026-10-01 17:25 UTCGHSA enrichment
  25. 2026-10-01 06:09 UTCVendor advisory
Show 73 more
  1. 2026-10-01 06:09 UTCGHSA enrichment
  2. 2026-09-30 18:52 UTCEG score recompute
  3. 2026-09-30 18:52 UTCVendor advisory
  4. 2026-09-30 18:52 UTCGHSA enrichment
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 07:35 UTCVendor advisory
  7. 2026-09-30 07:35 UTCGHSA enrichment
  8. 2026-09-29 20:18 UTCEG score recompute
  9. 2026-09-29 20:18 UTCVendor advisory
  10. 2026-09-29 20:18 UTCGHSA enrichment
  11. 2026-09-29 07:56 UTCEG score recompute
  12. 2026-09-29 07:56 UTCVendor advisory
  13. 2026-09-29 07:56 UTCGHSA enrichment
  14. 2026-09-28 20:39 UTCEG score recompute
  15. 2026-09-28 20:39 UTCVendor advisory
  16. 2026-09-28 20:39 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 09:22 UTCVendor advisory
  20. 2026-09-28 09:22 UTCGHSA enrichment
  21. 2026-09-27 22:06 UTCEG score recompute
  22. 2026-09-27 22:06 UTCVendor advisory
  23. 2026-09-27 22:05 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 10:48 UTCVendor advisory
  26. 2026-09-27 10:48 UTCGHSA enrichment
  27. 2026-09-26 23:32 UTCEG score recompute
  28. 2026-09-26 23:32 UTCVendor advisory
  29. 2026-09-26 23:32 UTCGHSA enrichment
  30. 2026-09-26 15:59 UTCEPSS rescore
  31. 2026-09-26 12:08 UTCVendor advisory
  32. 2026-09-26 12:08 UTCGHSA enrichment
  33. 2026-09-26 00:51 UTCEG score recompute
  34. 2026-09-26 00:51 UTCVendor advisory
  35. 2026-09-26 00:51 UTCGHSA enrichment
  36. 2026-09-25 13:08 UTCVendor advisory
  37. 2026-09-25 13:08 UTCGHSA enrichment
  38. 2026-09-25 01:52 UTCVendor advisory
  39. 2026-09-25 01:52 UTCGHSA enrichment
  40. 2026-09-24 14:35 UTCEG score recompute
  41. 2026-09-24 14:35 UTCVendor advisory
  42. 2026-09-24 14:35 UTCGHSA enrichment
  43. 2026-09-24 14:04 UTCEPSS rescore
  44. 2026-09-24 13:32 UTCVendor advisory
  45. 2026-09-24 13:32 UTCGHSA enrichment
  46. 2026-09-24 02:15 UTCEG score recompute
  47. 2026-09-24 02:14 UTCGHSA enrichment
  48. 2026-09-23 17:54 UTCEPSS rescore
  49. 2026-09-23 14:57 UTCGHSA enrichment
  50. 2026-09-23 03:41 UTCEG score recompute
  51. 2026-09-23 03:41 UTCGHSA enrichment
  52. 2026-09-22 16:24 UTCEG score recompute
  53. 2026-09-22 16:24 UTCGHSA enrichment
  54. 2026-09-22 16:01 UTCEPSS rescore
  55. 2026-09-22 15:40 UTCEG score recompute▲ 8.10
  56. 2026-09-22 15:40 UTCGHSA enrichment
  57. 2026-09-22 15:39 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  58. 2026-09-22 07:58 UTCGHSA enrichment
  59. 2026-09-21 21:09 UTCEPSS rescore
  60. 2026-09-20 20:16 UTCEPSS rescore
  61. 2026-09-19 13:59 UTCGHSA enrichment
  62. 2026-09-18 19:28 UTCEPSS rescore
  63. 2026-09-17 19:32 UTCEPSS rescore
  64. 2026-09-16 19:57 UTCGHSA enrichment
  65. 2026-09-16 15:26 UTCGHSA enrichment
  66. 2026-09-16 15:23 UTCNVD update
  67. 2026-09-16 14:36 UTCEG score recompute
  68. 2026-09-16 14:36 UTCGHSA enrichment
  69. 2026-09-16 14:35 UTCMITRE cvelistV5
  70. 2026-09-16 14:09 UTCEPSS rescore
  71. 2026-09-15 20:32 UTCNVD update
  72. 2026-09-15 19:48 UTCEG score recompute
  73. 2026-09-15 19:47 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-92239?
CVE-2026-92239 is a high vulnerability published on September 15, 2026. A maliciously constructed IMAP line could cause an out-of-bounds buffer read. This vulnerability was fixed in Thunderbird 156, Thunderbird 140.16, and Thunderbird 153.3.
When was CVE-2026-92239 disclosed?
CVE-2026-92239 was first published on September 15, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92239 actively exploited?
CVE-2026-92239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92239?
CVE-2026-92239 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-92239?
A fix for CVE-2026-92239 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92239 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92239

Explore →

Is Your Infrastructure Affected by CVE-2026-92239?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs