UBUNTU-CVE-2026-126136: Medium severity ubuntu/thunderbird vulnerability

Published Nov 12, 2026
·
Updated

For Exchange accounts using EWS or Microsoft Graph with OAuth2 authentication, Thunderbird sent the OAuth2 access token to the server even when the configured server URL used unencrypted HTTP. An attacker able to observe network traffic could obtain the token and use it to access the user's mailbox until the token expired. An attacker positioned on the network during account setup could cause such a URL to be configured. This vulnerability was fixed in Thunderbird 160 and Thunderbird 153.7.

Affected Software

4 affected components
ubuntu/thunderbird*
ubuntu/thunderbird*
ubuntu/thunderbird*
ubuntu/thunderbird*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Thunderbird to a version that resolves this vulnerability.

    Fixed in 160
  2. Upgrade

    Upgrade Thunderbird to a version that resolves this vulnerability.

    Fixed in 153.7

Event History

Nov 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Exchange accounts configured in Thunderbird to use EWS or Microsoft Graph with OAuth2 authentication are exposed if their configured server URL uses unencrypted HTTP. The impact is limited to users whose OAuth2 token can be observed on the network.

2

What does an attacker need to exploit it?

An attacker must be able to observe the victim's network traffic when Thunderbird sends the OAuth2 access token over HTTP. An attacker present on the network during account setup could also cause an unencrypted server URL to be configured.

3

What can an attacker do with a captured token?

A captured OAuth2 access token can be used to access the user's mailbox until that token expires.

4

What should be checked if updating is not immediately possible?

Check Exchange account configurations using EWS or Microsoft Graph with OAuth2 and ensure their server URLs use HTTPS rather than unencrypted HTTP. Avoid configuring or accepting HTTP server URLs during account setup.

5

Which Thunderbird releases contain the fix?

The issue was fixed in Thunderbird 160 and Thunderbird 153.7.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203