CVE-2026-126136: OAuth2 access token could be sent over an unencrypted connection with Exchange accounts
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 160 - Upgrade
Upgrade
Thunderbirdto a version that resolves this vulnerability.Fixed in 160
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-126132
- CVE-2026-126133
- CVE-2026-126134
- CVE-2026-126135
- CVE-2026-126136
- CVE-2026-120572
- CVE-2026-124852
- CVE-2026-124853
- CVE-2026-124854
- CVE-2026-124855
- CVE-2026-124856
- CVE-2026-124857
- CVE-2026-124858
- CVE-2026-124859
- CVE-2026-124860
- CVE-2026-124861
- CVE-2026-124862
- CVE-2026-124863
- CVE-2026-124864
- CVE-2026-124865
- CVE-2026-124866
- CVE-2026-124867
- CVE-2026-124868
- CVE-2026-124869
- CVE-2026-124870
- CVE-2026-124871
- CVE-2026-124872
- CVE-2026-124873
- CVE-2026-124874
- CVE-2026-124875
- CVE-2026-124876
- CVE-2026-124877
- CVE-2026-124878
- CVE-2026-124879
- CVE-2026-124880
- CVE-2026-124881
- CVE-2026-124882
- CVE-2026-124883
- CVE-2026-124884
- CVE-2026-124885
- CVE-2026-124886
- CVE-2026-124887
- CVE-2026-124888
- CVE-2026-124889
- CVE-2026-124890
- CVE-2026-124891
- CVE-2026-124892
- CVE-2026-124893
- CVE-2026-124894
- CVE-2026-124895
- CVE-2026-124896
- CVE-2026-124897
- CVE-2026-124898
- CVE-2026-124899
- CVE-2026-124900
- CVE-2026-124901
- CVE-2026-124902
- CVE-2026-124903
- CVE-2026-124904
- CVE-2026-124905
- CVE-2026-124906
- CVE-2026-124907
- CVE-2026-124908
- CVE-2026-124909
- CVE-2026-124910
- CVE-2026-124912
- CVE-2026-124913
- CVE-2026-124914
- CVE-2026-124915
- CVE-2026-124917
- CVE-2026-124918
- CVE-2026-124919
- CVE-2026-124920
- CVE-2026-124921
- CVE-2026-124922
- CVE-2026-124923
- CVE-2026-124924
- CVE-2026-124925
- CVE-2026-124926
- CVE-2026-124927
- CVE-2026-124928
- CVE-2026-124929
- CVE-2026-124930
- CVE-2026-124931
- CVE-2026-124932
- CVE-2026-124933
- CVE-2026-124934
- CVE-2026-124935
- CVE-2026-124936
- CVE-2026-124938
- CVE-2026-124939
- CVE-2026-124940
- CVE-2026-124941
- CVE-2026-124942
- CVE-2026-124943
- CVE-2026-124944
- CVE-2026-124945
- CVE-2026-124946
- CVE-2026-124947
- CVE-2026-124948
- CVE-2026-124949
- CVE-2026-124950
- CVE-2026-124951
Frequently Asked Questions
Which Thunderbird configurations are exposed?
The issue affects Exchange accounts that use EWS or Microsoft Graph with OAuth2 authentication when their configured server URL uses unencrypted HTTP. Accounts using other protocols or authentication methods are not identified as affected by the provided information.
What does an attacker need to exploit this?
An attacker must be able to observe network traffic to capture the OAuth2 access token sent over HTTP. An attacker positioned on the network during account setup could also cause an unencrypted server URL to be configured.
What is the impact if a token is captured?
A captured OAuth2 access token can be used to access the user's mailbox until that token expires.
How can this be remediated?
Update to Thunderbird 160, where this issue was fixed. Also ensure affected Exchange EWS or Microsoft Graph account server URLs use encrypted HTTPS rather than HTTP.