CVE-2025-3877

thunderbird: Rejected reason: This CVE was marked as fixed, but due to other code landing - was not actually fixed

CVE-2025-3877 is fixed in 2 products on 1 platform, first by CVE-2025-3877, released May 14, 2025. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
8.8
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
n/a

Rejected reason: This CVE was marked as fixed, but due to other code landing - was not actually fixed. It was subsequently fixed in CVE-2025-5986.

Where it's fixed

ProductFixed inFixReleased
Linux
MozillaThunderbird · opensuse-leap 15.6 128.10.1-150200.8.215.1 SUSE-SU-2025:01660-1 May 22, 2025
MozillaThunderbird · sles 15.6 128.10.1-150200.8.215.1 SUSE-SU-2025:01660-1 May 22, 2025
MozillaThunderbird · sles 15.7 128.10.1-150200.8.215.1 SUSE-SU-2025:01660-2 May 29, 2025
thunderbird · Debian 11.6 (bullseye) 1:128.10.1esr-1~deb11u1 CVE-2025-3877 May 14, 2025
thunderbird · Debian 12.15 (bookworm) 1:128.10.1esr-1~deb12u1 CVE-2025-3877 May 14, 2025
thunderbird · Debian 13.5 (trixie) 1:128.10.1esr-1 CVE-2025-3877 May 14, 2025
thunderbird · RHEL 8 0:128.11.0-1.el8_10 RHSA-2025:8756 Jun 10, 2025
thunderbird · RHEL 9 0:128.10.1-1.el9_6 RHSA-2025:8203 May 27, 2025
thunderbird · almalinux 10 128.10.1-1.el10_0.alma.1 ALSA-2025:8196 May 27, 2025
thunderbird · almalinux 8 128.11.0-1.el8_10.alma.1 ALSA-2025:8756 Jun 10, 2025
thunderbird · ol 10 0:128.11.0-1.0.1.el10_0 ELSA-2025-8196 Jun 30, 2025
thunderbird · ol 8 0:128.11.0-1.0.1.el8_10 ELSA-2025-8756 Jun 10, 2025
thunderbird · ol 9 0:128.10.1-1.0.1.el9_6 ELSA-2025-8203 May 27, 2025
thunderbird · rocky 10 0:128.10.1-1.el10_0 RLSA-2025:8196 Oct 3, 2025
thunderbird · rocky 8 0:128.11.0-1.el8_10 RLSA-2025:8756 Jul 29, 2025
thunderbird · rocky 9 0:128.10.1-1.el9_6 RLSA-2025:8203 Oct 4, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.