Skip to main content
CVE-2025-5262VulnerabilityPublished Updated

CVE-2025-5262: Mozilla Thunderbird · Double-free in libvpx encoder

Affects Mozilla ThunderbirdSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 139 or 128.11 soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 139, 128.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade Mozilla Thunderbird to 139 or 128.11.

Affected software

ProductAffectedFixed in
Mozilla ThunderbirdAffected
  • <139
  • <128.11
Fixed in
  • 139
  • 128.11

AI-suggested

To mitigate CVE-2025-5262, European organizations should prioritize updating Mozilla Thunderbird to versions 139 or later, or at least 128.11 or later, where the vulnerability has been addressed. In the absence of an immediate patch, organizations should consider disabling WebRTC functionality within Thunderbird to prevent triggering the vulnerable code path. Network-level controls such as filtering or blocking suspicious WebRTC traffic can reduce exposure. Employing application sandboxing or running Thunderbird with least privilege can limit the impact of potential exploitation. Monitoring Thunderbird process crashes and unusual behavior can provide early detection of exploitation attempts. Additionally, organizations should ensure that endpoint protection solutions are up to date and capable of detecting exploitation techniques related to memory corruption. Regular security awareness training for users to recognize phishing or malicious email attachments that could trigger WebRTC streams is also recommended. Finally, maintaining robust backup and incident response plans will help mitigate the impact if exploitation occurs.

Description

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.

References

Community reviews

Loading reviews…