Skip to main content
CVE-2023-2858VulnerabilityPublished Updated

CVE-2023-2858: Buffer over-read in Wireshark

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.0.6 or 3.6.14 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.6, 3.6.14
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 May 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade wireshark/wireshark to 4.0.6 or 3.6.14.

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • <3.6.14
  • <4.0.6
Fixed in
  • 3.6.14
  • 4.0.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Wireshark to versions later than 3.6.13 or 4.0.5 as soon as official patches are released to address CVE-2023-2858. 2. If you cannot patch yet, avoid opening capture files from untrusted or unknown sources to minimize exposure to crafted malicious files. 3. Implement sandboxing or containerization for Wireshark instances to isolate potential crashes and prevent broader system impact. 4. Employ strict access controls and monitoring on systems used for network analysis to detect anomalous activity or repeated crashes. 5. Educate security teams about the risk of opening unverified capture files and establish procedures for verifying file integrity before analysis. 6. Consider using alternative packet analysis tools or offline analysis methods for suspicious capture files until the vulnerability is mitigated. 7. Maintain updated incident response plans that include handling denial of service scenarios affecting security tools.

Description

NetScaler file parser crash in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via crafted capture file

References

Community reviews

Loading reviews…