CVE-2026-92035: thunderbird security update
Affects thunderbirdSource GCVE Database
Not known to be exploited · CVSS 9.6 Critical : upgrade to 140.17.0-1.el8_10.alma.1 as a priority.
Data as of 27 Oct 2026, 22:01 UTC
- Patch
- Available – fixed in 140.17.0-1.el8_10.alma.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade the AlmaLinux thunderbird package to 140.17.0-1.el8_10.alma.1.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlmaLinux 8thunderbird | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A security update is available and should be applied promptly. The fixed version is 140.17.0-1.el8_10.alma.1. Users should upgrade to this version or later to remediate the vulnerabilities. No additional mitigations are indicated by the vendor advisory.
Description
Multiple security vulnerabilities affecting Mozilla Thunderbird have been addressed in an important update. These include sandbox escapes, use-after-free bugs, privilege escalations, information disclosures, and other memory safety issues across various components such as Graphics, JavaScript, DOM, Networking, and Audio/Video. The update fixes these issues to improve the security posture of Thunderbird.
References
- access.redhat.com/errata/RHSA-2026:90913 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100756 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100757 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100758 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100759 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100762 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100766 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100767 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100769 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100770 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100771 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100772 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100773 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100774 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100775 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100776 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100777 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100778 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100779 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-100780 (opens in a new tab)