Skip to main content
Mallory
HighVulnerability

CVE-2021-22191: Improper URL Handling RCE in Wireshark 3.4.x/3.2.x

Published Mar 15, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS3.7%90th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Debian ProjectWireshark FoundationOracle Corporation
IdentifiersCVE-2021-22191CWE-20

CVE-2021-22191 is a vulnerability in Wireshark versions 3.4.0 to 3.4.3 and 3.2.0 to 3.2.11, where improper handling of URLs could allow an attacker to achieve remote code execution. The vulnerability can be triggered by injecting malicious packets or by providing a specially crafted capture file that, when opened in a vulnerable version of Wireshark, results in execution of arbitrary code.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to execute arbitrary code on the system running Wireshark, potentially leading to full system compromise. The attack can be performed remotely by sending malicious packets to be captured or by convincing a user to open a crafted capture file.

Mitigation

If you can’t patch tonight, do this now.

Do not open untrusted capture files or analyze network traffic from untrusted sources with vulnerable versions of Wireshark. Restrict access to Wireshark and ensure it is run with the least privileges necessary.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 3.4.4 or later, or 3.2.12 or later, where the improper URL handling issue has been fixed.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
Oracle CorporationZfs Storage Applianceoperating_system
Wireshark FoundationWiresharkapplication
FAQ

Frequently asked questions

Is CVE-2021-22191 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-22191 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-22191?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2021-22191.
Is there a patch for CVE-2021-22191?
Upgrade Wireshark to version 3.4.4 or later, or 3.2.12 or later, where the improper URL handling issue has been fixed.
What products are affected by CVE-2021-22191?
Wireshark Foundation Wireshark, Debian Project Debian Linux, and Oracle Corporation Zfs Storage Appliance.
How severe is CVE-2021-22191?
CVE-2021-22191 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 3.7% (90th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.