Different settings lead to different risks
Mozilla’s Thunderbird 160 security advisory lists four moderate issues that affect different features: calendar credentials and HTTP proxy authentication (CVE-2026-126133), Windows feed subscriptions and NTLM (CVE-2026-126134), SMTP or POP3 STARTTLS response handling (CVE-2026-126135), and OAuth2 tokens for Exchange accounts with an HTTP URL (CVE-2026-126136).
These flaws do not mean every Thunderbird installation is exposed in the same way. The affected configuration, operating system and network position differ. Use the individual advisory details to decide which checks apply to each device group.
Check the clients your team actually uses
Inventory Thunderbird versions and account settings through device management. Include Exchange OAuth2 accounts, CalDAV and ICS calendars, HTTP proxies, STARTTLS mail connections and Windows feed subscriptions. Ask administrators to verify configuration templates and onboarding instructions.
If an account used an unsafe URL or an untrusted proxy, ask the service owner whether token or password rotation is needed. Review access logs in line with your incident process.
Roll out the fixed release
Mozilla lists Thunderbird 160 as the fixed release. Use the supported update channel, restart the client and confirm the version across managed devices. Test mail send and receive, calendar sync and configured feeds after the rollout.
Record which client groups were checked and which settings changed. This gives support teams a clear response if a user reports a connection issue after the update.
