Application crash via freed BPv7 endpoint address
Published Nov 26, 2025 · Updated Mar 27, 2026
Use-after-free in the BPv7 dissector in Wireshark 4.6.0 allows attackers to crash the application via malformed packet data. The BPv7 cleanup path frees endpoint-address storage that remains referenced by conversation state, and a later TCPCL lookup reads it. Triggering the crash requires injected malformed live traffic or user interaction to open a malformed trace file; no data disclosure or modification is reported.
Summary
What happened
Use-after-free in the BPv7 dissector in Wireshark 4.6.0 allows attackers to crash the application via malformed packet data. The BPv7 cleanup path frees endpoint-address storage that remains referenced by conversation state, and a later TCPCL lookup reads it. Triggering the crash requires injected malformed live traffic or user interaction to open a malformed trace file; no data disclosure or modification is reported.
The record
- CVE
- CVE-2025-13674
- Published
- Nov 26, 2025
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-824, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo