CVE-2026-95388
Description
A flaw was found in Wireshark. A heap-based buffer overflow in the sharkd utility can cause the application to crash, resulting in a Denial of Service (DoS). An attacker could exploit this vulnerability by convincing a user to process specially crafted input.
Mitigation
To mitigate this flaw, restrict access to the sharkd daemon or remove the package if it is not required:
1. Terminate running sharkd processes if daemonized packet analysis is not required:
killall sharkd
2. If sharkd must be run over a network socket, bind it only to localhost or restrict incoming network traffic to trusted hosts using firewall rules:
firewall-cmd --remove-port=<port>/tcp --permanent
firewall-cmd --reload
Warning: Reloading firewall rules may temporarily disrupt active network connections.
3. If Wireshark command-line utilities are not necessary, remove the package providing the tool:
dnf remove wireshark-cli
Caveat: Removing wireshark-cli will remove related packet capture and dissection tools such as tshark.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.5 |
| Attack Vector | Network | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
