CVE-2025-13945
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-03

Last updated on: 2025-12-05

Assigner: GitLab Inc.

Description
HTTP3 dissector crash in Wireshark 4.6.0 and 4.6.1 allows denial of service
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-03
Last Modified
2025-12-05
Generated
2026-06-16
AI Q&A
2025-12-03
EPSS Evaluated
2026-06-14
NVD
CVE-2025-13945
EUVD
EUVD-2025-200733
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wireshark wireshark From 4.6.0 (inc) to 4.6.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1325 The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-13945 is a vulnerability in Wireshark versions 4.6.0 and 4.6.1 where the HTTP/3 dissector crashes or causes the application to freeze and use excessive CPU when processing a decrypted HTTP/3 conversation containing a HEADERS frame with many headers. This happens when loading a capture file with an injected SSLKEYLOG file, leading to denial of service by making Wireshark unresponsive. [1]

Impact Analysis

This vulnerability can cause Wireshark to freeze and consume high CPU resources when analyzing certain HTTP/3 traffic captures, resulting in denial of service. This can disrupt network analysis and troubleshooting activities, potentially delaying incident response or forensic investigations. [1]

Detection Guidance

This vulnerability can be detected by analyzing Wireshark behavior when processing decrypted HTTP/3 traffic containing HEADERS frames with a large number of headers. Specifically, loading a capture file (e.g., qpack.pcapng) with an injected SSLKEYLOG file in Wireshark versions 4.6.0 or 4.6.1 may cause the application to freeze or exhibit high CPU usage. To detect this, you can attempt to load such a capture file in the affected Wireshark versions and observe for freezes or excessive CPU consumption. There are no specific commands provided for detection in the resources. [1]

Mitigation Strategies

Immediate mitigation steps include avoiding the use of Wireshark versions 4.6.0 and 4.6.1 for analyzing decrypted HTTP/3 traffic with large HEADERS frames. Consider upgrading to a fixed version of Wireshark once available or refrain from loading capture files that trigger the issue. Monitoring for updates or patches from the Wireshark Foundation is recommended. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-13945. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart