Buffer Over-read in Wireshark

Why this deserves its current priority

A CVSS score is not reported in the current record. 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. Update Wireshark Foundation/Wireshark to 4.6.4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Feb 25, 2026

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

2. Source modified

   Sep 17, 2026

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

3. First seen by HOL

   Sep 17, 2026

Sources and claim methodology

• Source referencegitlab.com
• Source referencewireshark.org

Related CVEs

• Stack-based Buffer Overflow Vulnerability in Linux (uldaq)Same generic ecosystem
• rabbitmq-c: size_t underflow in AMQP frame length computation leads to out-of-bounds readSame generic ecosystem
• rabbitmq-c: Heap buffer overflow in AMQP login handshake via undersized connection.tune.frame_maxSame generic ecosystem
• Omni: TOCTOU race condition allows multiple concurrent uses of a single-use SAML session tokenSame generic ecosystem
• Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematicSame generic ecosystem
• Omni: Reader-level users can retrieve imported cluster CA keys via ResourceServiceSame generic ecosystem