Linux · 
Rocky Linux · Security advisory · October 3, 2025
Rocky Linux · Security advisory · October 3, 2025RLSA-2025:8608: thunderbird security update
RLSA-2025:8608, released October 3, 2025, fixes 9 CVEs in thunderbird (version 0:128.11.0-1.el10_0). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
9
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0952
95th percentile
Priority of the 9 CVEs
Patch now 0
Urgent 0
High 9
Routine 0
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| thunderbird | rocky 10 | 0:128.11.0-1.el10_0 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2025-4918 | Out-of-bounds access when resolving Promise objects | 9.8 | 0.0952 | None reported |
| High | CVE-2025-4919 | Out-of-bounds access when optimizing linear sums | 8.8 | 0.0912 | None reported |
| High | CVE-2025-5283 | Chromium: CVE-2025-5283 Use after free in libvpx | 8.8 | 0.0064 | None reported |
| High | CVE-2025-5268 | Memory safety bugs fixed in Firefox 139, Thunderbird 139, Firefox ESR 128.11, and Thunderbird 128.11 | 8.8 | 0.0051 | None reported |
| High | CVE-2025-5269 | Memory safety bug fixed in Firefox ESR 128.11 and Thunderbird 128.11 | 8.8 | 0.0048 | None reported |
| High | CVE-2025-5266 | Script element events leaked cross-origin resource status | 8.8 | 0.0034 | None reported |
| High | CVE-2025-5264 | Potential local code execution in “Copy as cURL” command | 8.8 | 0.0030 | None reported |
| High | CVE-2025-5267 | Clickjacking vulnerability could have led to leaking saved payment card details | 8.8 | 0.0028 | None reported |
| High | CVE-2025-5263 | Error handling for script execution was incorrectly isolated from web content | 8.8 | 0.0027 | None reported |
Showing 1 to 9 of 9
1
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.