Skip to main content
VulnerabilityPublished

CVE-2026-118180: thunderbird · When Logging

Affects thunderbirdSource GCVE Database

0
Authoritative record:CVE-2026-118180· High

Not known to be exploited : upgrade to 159 or 153.6 soon.

Data as of 27 Oct 2026, 22:13 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 159, 153.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 Ubuntu ubuntu/thunderbird package to 159 or 153.6.

Affected software

ProductAffectedFixed in
Ubuntuubuntu/thunderbirdpkg:deb/ubuntu/thunderbirdOther threatsAffected
  • <153.6
  • <159
Fixed in
  • 153.6
  • 159

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability has been fixed in Thunderbird versions 159 and 153.6. Users should upgrade to these versions or later to mitigate the risk. No additional action is required if the software is updated.

Description

Thunderbird versions prior to 159 and 153.6 had a vulnerability where the homeserver address provided in the Matrix login response was not validated. A malicious or compromised homeserver could supply a file: URL, causing Thunderbird to redirect Matrix requests to local files or, on Windows, to an attacker-controlled network share, potentially leaking the user's NTLM credentials. This NTLM credential leak affects only Thunderbird on Windows. The issue was fixed in Thunderbird 159 and 153.6.

References

Community reviews

Loading reviews…