CVE-2025-13499Public exploit

Application crash via unset Snappy decompression output

Published Nov 21, 2025 · Updated Nov 21, 2025

Access of an uninitialized pointer in Wireshark 4.6.0 and 4.4.0 through 4.4.10 allows attackers to crash the application via Kafka traffic. The Kafka dissector’s decompress_snappy function reports success for Snappy data containing no Xerial chunks without setting its output buffer, and later code asserts on the uninitialized tvbuff. Triggering the crash requires a malformed packet injected onto a monitored network or user interaction to open a malformed packet trace file; the reported consequence is a service interrupt.

CVSS severity7.8
High
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Access of an uninitialized pointer in Wireshark 4.6.0 and 4.4.0 through 4.4.10 allows attackers to crash the application via Kafka traffic. The Kafka dissector’s decompress_snappy function reports success for Snappy data containing no Xerial chunks without setting its output buffer, and later code asserts on the uninitialized tvbuff. Triggering the crash requires a malformed packet injected onto a monitored network or user interaction to open a malformed packet trace file; the reported consequence is a service interrupt.

The record

CVE
CVE-2025-13499
Published
Nov 21, 2025
Updated
Nov 21, 2025
Vendor
Wireshark Foundation
Product
Wireshark
Classifications
CWE-824, T1499.004, T1203
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 21, 2025CVE publishedPublication date reported by the CVE source.
  2. Nov 21, 2025Record 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.

  1. Affected versionversion=4.4.0 <4.4.11
  2. Affected versionversion=4.6.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Wireshark Foundation · Wiresharkversion=4.4.0 <4.4.11; version=4.6.0

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
7.8GitLab Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-824Access of Uninitialized Pointer
T1499.004Application or System Exploitation
T1203Exploitation for Client Execution

Public exploit references

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