CVE-2026-92238

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A maliciously constructed mail header could lead to multiple fields being parsed as one, or potential memory safety violations. This vulnerability was fixed in Thunderbird 156, Thunderbird 140.16, and Thunderbird 153.3.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 22, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
No patch confirmed yet.
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=2060601

Vendor Advisories for CVE-2026-92238(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 32× 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-09-24 03:56 UTCGHSA enrichment
  2. 2026-09-23 23:53 UTCGHSA enrichment
  3. 2026-09-23 19:51 UTCEG score recompute
  4. 2026-09-23 19:51 UTCGHSA enrichment
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-23 15:48 UTCGHSA enrichment
  7. 2026-09-23 11:46 UTCGHSA enrichment
  8. 2026-09-23 07:43 UTCGHSA enrichment
  9. 2026-09-23 03:40 UTCGHSA enrichment
  10. 2026-09-22 23:38 UTCEG score recompute
  11. 2026-09-22 23:38 UTCGHSA enrichment
  12. 2026-09-22 19:35 UTCGHSA enrichment
  13. 2026-09-22 18:53 UTCEG score recompute▲ 9.80
  14. 2026-09-22 18:53 UTCGHSA enrichment
  15. 2026-09-22 18:53 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  16. 2026-09-22 16:01 UTCEPSS rescore
  17. 2026-09-22 05:38 UTCGHSA enrichment
  18. 2026-09-21 21:09 UTCEPSS rescore
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-19 12:47 UTCGHSA enrichment
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-17 19:32 UTCEPSS rescore
  23. 2026-09-16 19:57 UTCGHSA enrichment
  24. 2026-09-16 15:26 UTCGHSA enrichment
  25. 2026-09-16 15:23 UTCNVD update
Show 7 more
  1. 2026-09-16 14:36 UTCEG score recompute
  2. 2026-09-16 14:36 UTCGHSA enrichment
  3. 2026-09-16 14:35 UTCMITRE cvelistV5
  4. 2026-09-16 14:09 UTCEPSS rescore
  5. 2026-09-15 20:32 UTCNVD update
  6. 2026-09-15 19:48 UTCEG score recompute
  7. 2026-09-15 19:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92238?
CVE-2026-92238 is a critical vulnerability published on September 15, 2026. A maliciously constructed mail header could lead to multiple fields being parsed as one, or potential memory safety violations. This vulnerability was fixed in Thunderbird 156, Thunderbird 140.16, and Thunderbird 153.3.
When was CVE-2026-92238 disclosed?
CVE-2026-92238 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92238 actively exploited?
CVE-2026-92238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.2% of all scored CVEs.
What is the CVSS score of CVE-2026-92238?
CVE-2026-92238 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-92238?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92238, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92238

Explore →

Is Your Infrastructure Affected by CVE-2026-92238?

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

Book a Demo →Browse All CVEs