BaseFortify

Publication date: 2025-12-09

Last updated on: 2026-04-13

Assigner: Mozilla Corporation

Description

Use-after-free in the WebRTC: Signaling component. This vulnerability was fixed in Firefox 146, Firefox ESR 140.6, Thunderbird 146, and Thunderbird 140.6.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-09

Last Modified

2026-04-13

Generated

2026-07-06

AI Q&A

2025-12-09

EPSS Evaluated

2026-07-05

NVD

CVE-2025-14321

Affected Vendors & Products

Vendor	Product	Version / Range
mozilla	firefox	to 140.6.0 (exc)
mozilla	firefox	to 146.0 (exc)
mozilla	thunderbird	to 140.6.0 (exc)
mozilla	thunderbird	to 146.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability is a use-after-free issue in the WebRTC signaling component of Firefox browsers. It affects versions of Firefox earlier than 146 and Firefox ESR earlier than 140.6. A use-after-free vulnerability occurs when a program continues to use memory after it has been freed, which can lead to unexpected behavior or exploitation.

Impact Analysis

This vulnerability could potentially allow an attacker to execute arbitrary code or cause a crash in the affected Firefox browsers by exploiting the use-after-free condition in the WebRTC signaling component. This could lead to compromise of the user's system or data.

Mitigation Strategies

To mitigate this vulnerability, you should update Firefox to version 146 or later, or Firefox ESR to version 140.6 or later, where the use-after-free issue in the WebRTC signaling component has been fixed. Applying these updates will address the improper memory handling and prevent potential exploitation. [2, 3]

Hi! I’m here to help you understand CVE-2025-14321. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70