Why this deserves its current priority

CVSS is 2.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. Update Wireshark Foundation/Wireshark to 4.6.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jul 8, 2026

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

2. Source modified

   Jul 9, 2026

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

3. First seen by HOL

   Jul 9, 2026

Sources and claim methodology

• Source referencegitlab.com
• Source referencewireshark.org

Related CVEs

• Langflow is affected by weaknesses in secret handling and sensitive configuration accessSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcementSame generic ecosystem
• Directus <12.1.0 - Authenticated time-based SQL injection in PostgreSQL/PostGIS collection creationSame generic ecosystem
• Langflow is affected OS Command Injection in Model Context Protocol featuresSame generic ecosystem
• Langflow is affected by OS Command Injection in Model Context Protocol featuresSame generic ecosystem
• Langflow is affected by security vulnerabilities in Model Context Protocol featuresSame generic ecosystem

Why this deserves its current priority

CVSS is 2.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. Update Wireshark Foundation/Wireshark to 4.6.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jul 8, 2026

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

2. Source modified

   Jul 9, 2026

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

3. First seen by HOL

   Jul 9, 2026

Sources and claim methodology

• Source referencegitlab.com
• Source referencewireshark.org

Related CVEs

• Langflow is affected by weaknesses in secret handling and sensitive configuration accessSame generic ecosystem
• Langflow OSS is affected by arbitrary code execution in custom component validation and trusted code enforcementSame generic ecosystem
• Directus <12.1.0 - Authenticated time-based SQL injection in PostgreSQL/PostGIS collection creationSame generic ecosystem
• Langflow is affected OS Command Injection in Model Context Protocol featuresSame generic ecosystem
• Langflow is affected by OS Command Injection in Model Context Protocol featuresSame generic ecosystem
• Langflow is affected by security vulnerabilities in Model Context Protocol featuresSame generic ecosystem