External risk intelligence

Thunderbird Calendar Location Leak and File Overwrite Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-118177

The vulnerability exists within the Thunderbird email client application, specifically during user-initiated account setup or calendar configuration. It is a client-side issue requiring user interaction to process specific calendar locations and is not a public-facing network service, edge gateway, or externally reachable infrastructure component.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Thunderbird that could allow a malicious server or network attacker to trick the application into subscribing to malicious calendar locations. This could potentially lead to the exposure of user credentials or unauthorized modification of local files on Windows systems. The primary concern at this stage is to confirm if this specific technology is in use and if it presents any relevant exposure.

  • Malicious calendar links can expose user credentials.
  • Sensitive information could be leaked or files altered.
  • Confirm if Thunderbird calendars are in use.

Attack Path

How an attacker could exploit the issue

An attacker could trick Thunderbird users into subscribing to a malicious calendar location during account setup or when adding a new network calendar. This could allow an attacker-controlled server or network attacker to intercept user credentials, potentially leading to unauthorized access or modification of local files.

  • User subscribes to attacker-controlled calendar.
  • Calendar refresh transmits credentials.
  • Credential theft and file modification.

Live Threat

Current exploitation, exposure, and threat context

When setting up accounts or adding network calendars, Thunderbird could be tricked into subscribing to malicious calendar locations. This could lead to the exposure of user credentials when the lookup uses plain HTTP, or allow an attacker to write changes to attacker-controlled locations.

  • User NTLM credentials could be at risk.
  • Malicious servers may redirect calendar lookups.
  • Attacker could overwrite local files or shares.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams should coordinate to identify and assess Thunderbird instances, prioritizing those that interact with untrusted network locations or local file paths. The immediate first step is to enumerate all Thunderbird deployments, confirm their reachability and business criticality, and assign an accountable owner for remediation planning.

  • Identify Thunderbird owners and business criticality.
  • Verify calendar subscription configurations and network access.
  • Plan remediation based on exposure and risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Thunderbird and how does it use calendars?

Thunderbird is a desktop email application that includes calendar functionality to help users organize events and tasks. Users can manage local calendars or connect to remote network calendars to synchronize scheduling data across different platforms and servers.

What is the vulnerability class for CVE-2026-118177?

This vulnerability is classified as CWE-601, known as a URL Redirection to Untrusted Site. Essentially, the software fails to properly validate the destination of a calendar subscription, allowing it to be directed toward arbitrary servers, local files, or unintended network shares.

How can an attacker trigger this Thunderbird issue?

An attacker triggers the bug by providing a malicious calendar location during the initial account setup or when a user adds a new network calendar. It is not triggered by standard email receipt; it specifically requires the application to process and subscribe to a path that points to an attacker-controlled resource.

Is my Thunderbird instance at risk based on Halo Surface Signal?

Halo Surface Signal indicates the risk is very unlikely because this is a client-side issue, not an externally reachable network service. Since the vulnerability requires user action during calendar configuration, it does not pose the same risk as an unauthenticated, internet-facing infrastructure component.

Do I need to update my software to fix this?

Yes, you should update. The first step is to identify all Thunderbird installations in your environment. Once you have a list of deployments, verify that they are running the latest versions where this issue has been resolved, specifically versions 159 or 153.6.

References