CVE-2025-5262
A double-free could have occurred in `vpx_codec_enc_init_multi` after a failed allocation when...
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 139 and Thunderbird < 128.11.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 139 and Thunderbird < 128.11.
- Record
CVE-2025-5262- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-415
- Updated
- 2026-11-02
EUVDEUVD-2025-25234
7.5
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 139 and Thunderbird < 128.11.
- Record
EUVD-2025-25234- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-v5j6-fjmw-w724
7.5
A double-free could have occurred in `vpx_codec_enc_init_multi` after a failed allocation when...
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Firefox < 139, Firefox ESR < 115.24, and Firefox ESR < 128.11.
- Record
GHSA-v5j6-fjmw-w724- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-415
- Updated
- 2026-11-02
NVD
7.5
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 139 and Thunderbird < 128.11.
- Record
CVE-2025-5262- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-415
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2025-5262
7.5
A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 139 and Thunderbird < 128.11.
- Record
UBUNTU-CVE-2025-5262- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVCLSA-2026-1785560172 No score
thunderbird: Fix of 255 CVEs
-
rebase from Thunderbird 115.4.1 to 140.12.0 ESR
-
CVE-2022-3032: When receiving an HTML email that contained an iframe element, which used a srcdoc attribute to define the inner HTML document, remote objects specified in the nested document, for example images or videos, were not blocked
-
CVE-2023-0430: Certificate OCSP revocation status was not checked when verifying S/Mime signatures
-
CVE-2023-0547: OCSP revocation status of recipient certificates was not checked when sending S/Mime encrypted email, and revoked certificates would be accepted
-
CVE-2023-0616: If a MIME email combines OpenPGP and OpenPGP MIME data in a certain way Thunderbird repeatedly attempts to process and display the message, which could cause Thunderbird's user interface to lock up and no longer respond to the user's actions
-
CVE-2023-1945: Unexpected data returned from the Safe Browsing API could have led to memory corruption and a potentially exploitable crash
-
CVE-2023-4573: When receiving rendering data over IPC
mStreamcould have been destroyed when initialized, which could have led to a use-after-free causing a potentially exploitable crash -
CVE-2023-4574: When creating a callback over IPC for showing the Color Picker window, multiple of the same callbacks could have been created at a time and eventually all simultaneously destroyed as soon as one of the callbacks finished
-
CVE-2023-4575: When creating a callback over IPC for showing the File Picker window, multiple of the same callbacks could have been created at a time and eventually all simultaneously destroyed as soon as one of the callbacks finished
-
CVE-2023-4577: When
UpdateRegExpStaticsattempted to accessinitialStringHeapit could already have been garbage collected prior to entering the function, which could potentially have led to an exploitable crash -
CVE-2023-4578: When calling
JS::CheckRegExpSyntaxa Syntax Error could have been set which would end in callingconvertToRuntimeErrorAndClear. A path in the function could attempt to allocate memory when none is available which would have caused a newly created Out of Memory exception to be mishandled as a Syntax Error -
CVE-2023-4580: Push notifications stored on disk in private browsing mode were not being encrypted potentially allowing the leak of sensitive information
-
CVE-2023-4581: Excel
.xlladd-in files did not have a blocklist entry in Firefox's executable blocklist which allowed them to be downloaded without any warning of their potential harm -
CVE-2023-5169: A compromised content process could have provided malicious data in a
PathRecordingresulting in an out-of-bounds write, leading to a potentially exploitable crash in a privileged process -
CVE-2023-5171: During Ion compilation, a Garbage Collection could have resulted in a use-after-free condition, allowing an attacker to write two NUL bytes, and cause a potentially exploitable crash
-
CVE-2023-5724: Drivers are not always robust to extremely large draw calls and in some cases this scenario could have led to a crash
-
CVE-2023-5725: A malicious installed WebExtension could open arbitrary URLs, which under the right circumstance could be leveraged to collect sensitive user data
-
CVE-2023-5732: An attacker could have created a malicious link using bidirectional characters to spoof the location in the address bar when visited
-
CVE-2023-6204: On some systems—depending on the graphics settings and drivers—it was possible to force an out-of-bounds read and leak memory data into the images created on the canvas element
-
CVE-2023-6205: It was possible to cause the use of a MessagePort after it had already been freed, which could potentially have led to an exploitable crash
-
CVE-2023-6206: The black fade animation when exiting fullscreen is roughly the length of the anti-clickjacking delay on permission prompts
-
CVE-2023-6207: Ownership…
- Record
CLSA-2026-1785560172- Updated
- 2026-11-02
Show 4 moreShow less
OSVMGASA-2025-0197 No score
Updated thunderbird packages fix security vulnerabilities
CVE-2025-5262: A double-free could have occurred in vpx_codec_enc_init_multi after a failed allocation when initializing the encoder for WebRTC. This could have caused memory corruption and a potentially exploitable crash. CVE-2025-5263: Error handling for script execution was incorrectly isolated from web content, which could have allowed cross-origin leak attacks. CVE-2025-5264: Due to insufficient escaping of the newline character in the “Copy as cURL” feature, an attacker could trick a user into using this command, potentially leading to local code execution on the user's system. CVE-2025-5266: Script elements loading cross-origin resources generated load and error events which leaked information enabling XS-Leaks attacks. CVE-2025-5267: A clickjacking vulnerability could have been used to trick a user into leaking saved payment card details to a malicious page. CVE-2025-5268: Memory safety bugs present in Firefox 138, Thunderbird 138, Firefox ESR 128.10, and Thunderbird 128.10. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. CVE-2025-5269: Memory safety bug present in Firefox ESR 128.10, and Thunderbird 128.10. This bug showed evidence of memory corruption and we presume that with enough effort this could have been exploited to run arbitrary code. CVE-2025-5986: A crafted HTML email using mailbox:/// links can trigger automatic, unsolicited downloads of .pdf files to the user's desktop or home directory without prompting, even if auto-saving is disabled. This behavior can be abused to fill the disk with garbage data (e.g. using /dev/urandom on Linux) or to leak Windows credentials via SMB links when the email is viewed in HTML mode. While user interaction is required to download the .pdf file, visual obfuscation can conceal the download trigger. Viewing the email in HTML mode is enough to load external content. We can't ship this update to armv7hl architecture, we are investigating the issue and will try to update thunderbird for armv7hl as soon as posible.
- Record
MGASA-2025-0197- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15170-1 No score
firefox-esr-128.11.0-1.1 on GA media
These are all security issues fixed in the firefox-esr-128.11.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15170-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15174-1 No score
MozillaThunderbird-128.11.0-1.1 on GA media
These are all security issues fixed in the MozillaThunderbird-128.11.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15174-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:01946-1 No score
Security update for MozillaThunderbird
This update for MozillaThunderbird fixes the following issues:
Update to Mozilla Thunderbird 128.11 (MFSA 2025-46, bsc#1243353):
- CVE-2025-5262: Double-free in libvpx encoder (bmo#1962421)
- CVE-2025-5263: Error handling for script execution was incorrectly isolated from web content (bmo#1960745)
- CVE-2025-5264: Potential local code execution in 'Copy as cURL' command (bmo#1950001)
- CVE-2025-5265: Potential local code execution in 'Copy as cURL' command (bmo#1962301)
- CVE-2025-5266: Script element events leaked cross-origin resource status (bmo#1965628)
- CVE-2025-5267: Clickjacking vulnerability could have led to leaking saved payment card details (bmo#1954137)
- CVE-2025-5268: Memory safety bugs fixed in Firefox 139, Thunderbird 139, Firefox ESR 128.11, and Thunderbird 128.11 (bmo#1950136, bmo#1958121, bmo#1960499, bmo#1962634)
- CVE-2025-5269: Memory safety bug fixed in Firefox ESR 128.11 and Thunderbird 128.11 (bmo#1924108)
- Record
SUSE-SU-2025:01946-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
thunderbirdTuxCare:AlmaLinux:9.2 From an advisory covering 253 CVEs |
before 140.12.0-1.el9_2.alma.1.tuxcare.els1 | 140.12.0-1.el9_2.alma.1.tuxcare.els1 |
thunderbirdMageia:9 From an advisory covering 8 CVEs |
before 128.11.1-1.1.mga9 | 128.11.1-1.1.mga9 |
thunderbird-l10nMageia:9 From an advisory covering 8 CVEs |
before 128.11.1-1.mga9 | 128.11.1-1.mga9 |
MozillaThunderbirdSUSE:Linux Enterprise Module for Package Hub 15 SP6 From an advisory covering 8 CVEs |
before 128.11.0-150200.8.221.1 | 128.11.0-150200.8.221.1 |
MozillaThunderbirdSUSE:Linux Enterprise Module for Package Hub 15 SP7 From an advisory covering 8 CVEs |
before 128.11.0-150200.8.221.1 | 128.11.0-150200.8.221.1 |
MozillaThunderbirdSUSE:Linux Enterprise Workstation Extension 15 SP6 From an advisory covering 8 CVEs |
before 128.11.0-150200.8.221.1 | 128.11.0-150200.8.221.1 |
MozillaThunderbirdSUSE:Linux Enterprise Workstation Extension 15 SP7 From an advisory covering 8 CVEs |
before 128.11.0-150200.8.221.1 | 128.11.0-150200.8.221.1 |
MozillaThunderbirdopenSUSE:Leap 15.6 From an advisory covering 8 CVEs |
before 128.11.0-150200.8.221.1 | 128.11.0-150200.8.221.1 |
mozjs52Ubuntu:18.04:LTS |
All versions, plus listed versions 52.3.1-0ubuntu352.3.1-7fakesync152.8.1-0ubuntu0.18.04.152.9.1-0ubuntu0.18.04.1 |
None known |
mozjs68Ubuntu:20.04:LTS |
All versions, plus listed versions 68.5.0-1~fakesync68.5.0-2~fakesync68.6.0-168.6.0-1ubuntu1 |
None known |
Show 8 moreShow less
| Package | Affected | Fixed |
|---|---|---|
mozjs52Ubuntu:20.04:LTS |
All versions, plus listed versions 52.9.1-1build152.9.1-1ubuntu3 |
None known |
mozjs102Ubuntu:22.04:LTS |
All versions, plus listed versions 102.11.0-0ubuntu0.22.04.1102.12.0-0ubuntu0.22.04.1102.13.0-0ubuntu0.22.04.1102.15.1-0ubuntu0.22.04.1 |
None known |
mozjs78Ubuntu:22.04:LTS |
All versions, plus listed versions 78.13.0-178.15.0-278.15.0-4ubuntu1 |
None known |
mozjs91Ubuntu:22.04:LTS |
All versions, plus listed versions 91.5.1-0ubuntu191.6.0-191.6.0-291.7.0-291.10.0-0ubuntu1 |
None known |
mozjs102Ubuntu:24.04:LTS |
All versions, plus listed versions 102.15.1-1102.15.1-3ubuntu2 |
None known |
mozjs115Ubuntu:24.04:LTS |
All versions, plus listed versions 115.3.0-0ubuntu1115.4.0-2115.5.0-1115.6.0-1115.7.0-4 Show 4 moreShow less115.8.0-1115.9.0-1115.9.0-1build1115.10.0-1 |
None known |
firefox-esropenSUSE:Tumbleweed From an advisory covering 8 CVEs |
before 128.11.0-1.1 | 128.11.0-1.1 |
MozillaThunderbirdopenSUSE:Tumbleweed From an advisory covering 8 CVEs |
before 128.11.0-1.1 | 128.11.0-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-5262 is a high vulnerability (CVSS 7.5) in Mozilla Thunderbird, published May 27, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.46%, the 40th percentile. No source names a fixed version.
References
bugzilla.mozilla.org/show_bug.cgi?id=1962421
mozilla.org/security/advisories/mfsa2025-45
mozilla.org/security/advisories/mfsa2025-46
nvd.nist.gov/vuln/detail/CVE-2025-5262
mozilla.org/security/advisories/mfsa2025-42
mozilla.org/security/advisories/mfsa2025-43
Show 194 moreShow less
mozilla.org/security/advisories/mfsa2025-44
github.com/advisories/GHSA-v5j6-fjmw-w724
errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1785560172.html
nvd.nist.gov/vuln/detail/CVE-2022-3032
nvd.nist.gov/vuln/detail/CVE-2023-0430
nvd.nist.gov/vuln/detail/CVE-2023-0547
nvd.nist.gov/vuln/detail/CVE-2023-0616
nvd.nist.gov/vuln/detail/CVE-2023-1945
nvd.nist.gov/vuln/detail/CVE-2023-23598
nvd.nist.gov/vuln/detail/CVE-2023-23599
nvd.nist.gov/vuln/detail/CVE-2023-23601
nvd.nist.gov/vuln/detail/CVE-2023-23602
nvd.nist.gov/vuln/detail/CVE-2023-25728
nvd.nist.gov/vuln/detail/CVE-2023-25730
nvd.nist.gov/vuln/detail/CVE-2023-25737
nvd.nist.gov/vuln/detail/CVE-2023-25742
nvd.nist.gov/vuln/detail/CVE-2023-25751
nvd.nist.gov/vuln/detail/CVE-2023-25752
nvd.nist.gov/vuln/detail/CVE-2023-28164
nvd.nist.gov/vuln/detail/CVE-2023-29533
nvd.nist.gov/vuln/detail/CVE-2023-29535
nvd.nist.gov/vuln/detail/CVE-2023-29536
nvd.nist.gov/vuln/detail/CVE-2023-29539
nvd.nist.gov/vuln/detail/CVE-2023-29548
nvd.nist.gov/vuln/detail/CVE-2023-32206
nvd.nist.gov/vuln/detail/CVE-2023-32211
nvd.nist.gov/vuln/detail/CVE-2023-37207
nvd.nist.gov/vuln/detail/CVE-2023-4573
nvd.nist.gov/vuln/detail/CVE-2023-4574
nvd.nist.gov/vuln/detail/CVE-2023-4575
nvd.nist.gov/vuln/detail/CVE-2023-4577
nvd.nist.gov/vuln/detail/CVE-2023-4578
nvd.nist.gov/vuln/detail/CVE-2023-4580
nvd.nist.gov/vuln/detail/CVE-2023-4581
nvd.nist.gov/vuln/detail/CVE-2023-50761
nvd.nist.gov/vuln/detail/CVE-2023-50762
nvd.nist.gov/vuln/detail/CVE-2023-5169
nvd.nist.gov/vuln/detail/CVE-2023-5171
nvd.nist.gov/vuln/detail/CVE-2023-5724
nvd.nist.gov/vuln/detail/CVE-2023-5725
nvd.nist.gov/vuln/detail/CVE-2023-5732
nvd.nist.gov/vuln/detail/CVE-2023-6204
nvd.nist.gov/vuln/detail/CVE-2023-6205
nvd.nist.gov/vuln/detail/CVE-2023-6206
nvd.nist.gov/vuln/detail/CVE-2023-6207
nvd.nist.gov/vuln/detail/CVE-2023-6208
nvd.nist.gov/vuln/detail/CVE-2023-6209
nvd.nist.gov/vuln/detail/CVE-2023-6212
nvd.nist.gov/vuln/detail/CVE-2023-6856
nvd.nist.gov/vuln/detail/CVE-2023-6857
nvd.nist.gov/vuln/detail/CVE-2023-6859
nvd.nist.gov/vuln/detail/CVE-2023-6860
nvd.nist.gov/vuln/detail/CVE-2023-6862
nvd.nist.gov/vuln/detail/CVE-2023-6863
nvd.nist.gov/vuln/detail/CVE-2023-6864
nvd.nist.gov/vuln/detail/CVE-2024-0746
nvd.nist.gov/vuln/detail/CVE-2024-0750
nvd.nist.gov/vuln/detail/CVE-2024-0751
nvd.nist.gov/vuln/detail/CVE-2024-10458
nvd.nist.gov/vuln/detail/CVE-2024-10459
nvd.nist.gov/vuln/detail/CVE-2024-10460
nvd.nist.gov/vuln/detail/CVE-2024-10461
nvd.nist.gov/vuln/detail/CVE-2024-10462
nvd.nist.gov/vuln/detail/CVE-2024-10463
nvd.nist.gov/vuln/detail/CVE-2024-10464
nvd.nist.gov/vuln/detail/CVE-2024-10465
nvd.nist.gov/vuln/detail/CVE-2024-10466
nvd.nist.gov/vuln/detail/CVE-2024-10467
nvd.nist.gov/vuln/detail/CVE-2024-10468
nvd.nist.gov/vuln/detail/CVE-2024-11159
nvd.nist.gov/vuln/detail/CVE-2024-11692
nvd.nist.gov/vuln/detail/CVE-2024-11693
nvd.nist.gov/vuln/detail/CVE-2024-11694
nvd.nist.gov/vuln/detail/CVE-2024-11695
nvd.nist.gov/vuln/detail/CVE-2024-11696
nvd.nist.gov/vuln/detail/CVE-2024-11697
nvd.nist.gov/vuln/detail/CVE-2024-11700
nvd.nist.gov/vuln/detail/CVE-2024-11701
nvd.nist.gov/vuln/detail/CVE-2024-11702
nvd.nist.gov/vuln/detail/CVE-2024-11704
nvd.nist.gov/vuln/detail/CVE-2024-11705
nvd.nist.gov/vuln/detail/CVE-2024-11706
nvd.nist.gov/vuln/detail/CVE-2024-11708
nvd.nist.gov/vuln/detail/CVE-2024-1546
nvd.nist.gov/vuln/detail/CVE-2024-1547
nvd.nist.gov/vuln/detail/CVE-2024-1548
nvd.nist.gov/vuln/detail/CVE-2024-1549
nvd.nist.gov/vuln/detail/CVE-2024-1550
nvd.nist.gov/vuln/detail/CVE-2024-1551
nvd.nist.gov/vuln/detail/CVE-2024-1553
nvd.nist.gov/vuln/detail/CVE-2024-2608
nvd.nist.gov/vuln/detail/CVE-2024-2609
nvd.nist.gov/vuln/detail/CVE-2024-2610
nvd.nist.gov/vuln/detail/CVE-2024-2611
nvd.nist.gov/vuln/detail/CVE-2024-2612
nvd.nist.gov/vuln/detail/CVE-2024-2614
nvd.nist.gov/vuln/detail/CVE-2024-2616
nvd.nist.gov/vuln/detail/CVE-2024-3302
nvd.nist.gov/vuln/detail/CVE-2024-3852
nvd.nist.gov/vuln/detail/CVE-2024-3857
nvd.nist.gov/vuln/detail/CVE-2024-3859
nvd.nist.gov/vuln/detail/CVE-2024-3861
nvd.nist.gov/vuln/detail/CVE-2024-3864
nvd.nist.gov/vuln/detail/CVE-2024-4767
nvd.nist.gov/vuln/detail/CVE-2024-4768
nvd.nist.gov/vuln/detail/CVE-2024-4769
nvd.nist.gov/vuln/detail/CVE-2024-4770
nvd.nist.gov/vuln/detail/CVE-2024-4777
nvd.nist.gov/vuln/detail/CVE-2024-5688
nvd.nist.gov/vuln/detail/CVE-2024-5690
nvd.nist.gov/vuln/detail/CVE-2024-5691
nvd.nist.gov/vuln/detail/CVE-2024-5693
nvd.nist.gov/vuln/detail/CVE-2024-5696
nvd.nist.gov/vuln/detail/CVE-2024-5700
nvd.nist.gov/vuln/detail/CVE-2024-6600
nvd.nist.gov/vuln/detail/CVE-2024-6601
nvd.nist.gov/vuln/detail/CVE-2024-6602
nvd.nist.gov/vuln/detail/CVE-2024-6603
nvd.nist.gov/vuln/detail/CVE-2024-6604
nvd.nist.gov/vuln/detail/CVE-2024-6606
nvd.nist.gov/vuln/detail/CVE-2024-6607
nvd.nist.gov/vuln/detail/CVE-2024-6608
nvd.nist.gov/vuln/detail/CVE-2024-6609
nvd.nist.gov/vuln/detail/CVE-2024-6610
nvd.nist.gov/vuln/detail/CVE-2024-6611
nvd.nist.gov/vuln/detail/CVE-2024-6612
nvd.nist.gov/vuln/detail/CVE-2024-6613
nvd.nist.gov/vuln/detail/CVE-2024-6614
nvd.nist.gov/vuln/detail/CVE-2024-6615
nvd.nist.gov/vuln/detail/CVE-2024-7518
nvd.nist.gov/vuln/detail/CVE-2024-7521
nvd.nist.gov/vuln/detail/CVE-2024-7522
nvd.nist.gov/vuln/detail/CVE-2024-7525
nvd.nist.gov/vuln/detail/CVE-2024-7526
nvd.nist.gov/vuln/detail/CVE-2024-7527
nvd.nist.gov/vuln/detail/CVE-2024-7529
nvd.nist.gov/vuln/detail/CVE-2024-7652
nvd.nist.gov/vuln/detail/CVE-2024-8394
nvd.nist.gov/vuln/detail/CVE-2024-9392
nvd.nist.gov/vuln/detail/CVE-2024-9393
nvd.nist.gov/vuln/detail/CVE-2024-9394
nvd.nist.gov/vuln/detail/CVE-2024-9396
nvd.nist.gov/vuln/detail/CVE-2024-9397
nvd.nist.gov/vuln/detail/CVE-2024-9398
nvd.nist.gov/vuln/detail/CVE-2024-9399
nvd.nist.gov/vuln/detail/CVE-2024-9400
nvd.nist.gov/vuln/detail/CVE-2024-9401
nvd.nist.gov/vuln/detail/CVE-2025-0237
nvd.nist.gov/vuln/detail/CVE-2025-0238
nvd.nist.gov/vuln/detail/CVE-2025-0239
nvd.nist.gov/vuln/detail/CVE-2025-0240
nvd.nist.gov/vuln/detail/CVE-2025-0241
nvd.nist.gov/vuln/detail/CVE-2025-0242
nvd.nist.gov/vuln/detail/CVE-2025-0247
nvd.nist.gov/vuln/detail/CVE-2025-0510
nvd.nist.gov/vuln/detail/CVE-2025-1009
nvd.nist.gov/vuln/detail/CVE-2025-1010
nvd.nist.gov/vuln/detail/CVE-2025-1012
nvd.nist.gov/vuln/detail/CVE-2025-1013
nvd.nist.gov/vuln/detail/CVE-2025-1014
nvd.nist.gov/vuln/detail/CVE-2025-1015
nvd.nist.gov/vuln/detail/CVE-2025-1016
nvd.nist.gov/vuln/detail/CVE-2025-1018
nvd.nist.gov/vuln/detail/CVE-2025-1019
nvd.nist.gov/vuln/detail/CVE-2025-10527
nvd.nist.gov/vuln/detail/CVE-2025-10528
nvd.nist.gov/vuln/detail/CVE-2025-10529
nvd.nist.gov/vuln/detail/CVE-2025-10532
nvd.nist.gov/vuln/detail/CVE-2025-10533
nvd.nist.gov/vuln/detail/CVE-2025-10536
nvd.nist.gov/vuln/detail/CVE-2025-11708
nvd.nist.gov/vuln/detail/CVE-2025-11709
nvd.nist.gov/vuln/detail/CVE-2025-11710
advisories.mageia.org/MGASA-2025-0197.html
bugs.mageia.org/show_bug.cgi?id=34338
thunderbird.net/en-US/thunderbird/128.11.0esr/releasenotes
mozilla.org/en-US/security/advisories/mfsa2025-46
thunderbird.net/en-US/thunderbird/128.11.1esr/releasenotes
mozilla.org/en-US/security/advisories/mfsa2025-49
suse.com/support/update/announcement/2025/suse-su-202501946-1
bugzilla.suse.com/1243353
suse.com/security/cve/CVE-2025-5262
suse.com/security/cve/CVE-2025-5263
suse.com/security/cve/CVE-2025-5264
suse.com/security/cve/CVE-2025-5265
suse.com/security/cve/CVE-2025-5266
suse.com/security/cve/CVE-2025-5267
suse.com/security/cve/CVE-2025-5268
suse.com/security/cve/CVE-2025-5269
ubuntu.com/security/CVE-2025-5262
cve.org/CVERecord?id=CVE-2025-5262
mozilla.org/en-US/security/advisories/mfsa2025-42
mozilla.org/en-US/security/advisories/mfsa2025-44
lists.opensuse.org/archives/list/[email protected]/thread/TEMWQQR3WLN7ACI6LZQ7KQO5GLIQ3HLM
Left out here: 84 references and the rest of 1 source description. The JSON record has them.