CVE-2026-130464
Description
A flaw was found in Wireshark. Malformed packets processed by the MsgPack or Network News Transfer Protocol (NNTP) dissectors can trigger an application crash. By injecting crafted traffic or tricking a user into opening a malicious packet capture file, an attacker can cause the application to terminate unexpectedly, resulting in a Denial of Service (DoS).
Statement
This vulnerability is rated as Moderate impact for Red Hat because successful exploitation requires user interaction to process a maliciously crafted packet capture or capture untrusted network traffic, restricting the blast radius to an application crash without arbitrary code execution or data exposure. Wireshark is an interactive diagnostic tool rather than an unattended network service, meaning an unexpected termination disrupts only the active inspection session. Furthermore, the issue only manifests when the specific MsgPack or NNTP dissectors parse malformed packets, leaving unrelated network protocol analysis unaffected.
Mitigation
Disable the MsgPack and NNTP dissectors when analyzing untrusted packet captures.
In the Wireshark graphical interface:
Navigate to Analyze > Enabled Protocols, locate "MsgPack" and "NNTP", clear their checkboxes, and click Save.
For the command-line utility (tshark), disable both dissectors at invocation:
tshark --disable-protocol msgpack --disable-protocol nntp -r <capture_file>
Alternatively, disable the protocols persistently by appending them to the Wireshark disabled protocols configuration file (~/.config/wireshark/disabled_protos):
msgpack
nntp
Caveats: Disabling these dissectors prevents decoding and structured analysis of MsgPack and NNTP traffic, presenting the data as unparsed payload. Any running Wireshark application instances must be restarted for configuration file changes to take effect.
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)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other 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.