Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-76921Published 2026-08-19

CVE-2026-76921 — Wireshark

medium

As of 2026-08-19, CVE-2026-76921 is a MEDIUM-severity vulnerability in Wireshark, CVSS v3.1 5.5. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-76921 as of 2026-08-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
5.5/10Medium
EPSS
—No EPSS score yet
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.8/10Threadlinqs triage score
Published
CVSS v3.1 5.5 (MEDIUM) · Priority 2.8/10 · Published 2026-08-19

Last updated:

What is CVE-2026-76921?

CMS protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

The record classifies CVE-2026-76921 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 47 days ago.

Severity and exploitation probability

CVSS v3.1 base score
5.5 — MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-19

Is CVE-2026-76921 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-76921

No vendor patch reference has been recorded for CVE-2026-76921 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-76921

No threat campaign in the Threadlinqs corpus currently references CVE-2026-76921, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org. Last verified by Threadlinqs on .

Other references