CVE-2026-130454
Description
A flaw was found in Wireshark. An attacker could trigger a Denial of Service (DoS) by convincing a user to open a specially crafted packet capture file or by injecting malformed IEEE 1905 network traffic. When processed, the malformed packets cause the IEEE 1905 protocol dissector (traffic parser) to crash, terminating the application.
Statement
This vulnerability is rated as having a Moderate impact because exploitation requires either convincing a user to open a malicious capture trace or actively inspecting untrusted network traffic, resulting exclusively in an application termination. In Red Hat Enterprise Linux environments, Wireshark is an interactive diagnostic utility executed on demand rather than a persistent system service, confining any denial of service solely to the active analysis session without compromising host confidentiality or integrity.
Mitigation
Disable the IEEE 1905 protocol dissector or refrain from inspecting packet captures from untrusted sources.
To disable the dissector in the Wireshark graphical interface:
1. Navigate to Analyze -> Enabled Protocols...
2. Search for the IEEE 1905 protocol and uncheck it.
For command-line analysis using tshark, disable the protocol at runtime:
tshark --disable-protocol ieee1905 -r <capture_file>
Caveats: Disabling the IEEE 1905 dissector prevents decoding of IEEE 1905 protocol frames. If packet analysis tools are not needed on the system, removing the wireshark package eliminates exposure.
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.5 | N/A | 5.5 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.