Buffer Over-read in Wireshark

Why this deserves its current priority

CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Wireshark Foundation/Wireshark (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Wireshark Foundation/Wireshark.
2. 2Review the reported fix. Source-reported solution: Upgrade to version 4.6.9 or above

Evidence timeline and material changes

1. Published upstream

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 29, 2026

Sources and claim methodology

• Source referencegitlab.com
• Source referencegitlab.com
• Source referencewireshark.org

Related CVEs

• Loop with Unreachable Exit Condition ('Infinite Loop') in WiresharkSame wireshark foundation/wireshark package
• Heap-based Buffer Overflow in WiresharkSame wireshark foundation/wireshark package
• Heap-based Buffer Overflow in WiresharkSame wireshark foundation/wireshark package
• Heap-based Buffer Overflow in WiresharkSame wireshark foundation/wireshark package
• NULL Pointer Dereference in WiresharkSame wireshark foundation/wireshark package
• Use After Free in WiresharkSame wireshark foundation/wireshark package