Wireshark denial of service in ERF file parser
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.10, 4.4.20
- Who is exposed
- Not reported
Summary
Wireshark, the network packet analyzer from the Wireshark Foundation, has an out-of-bounds read flaw in its ERF file parser that can crash the program and cause a denial of service. An attacker would need to get a user to open a crafted ERF file locally.
Written by a model
Original description
ERF file parser crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service
What to do
Upgrade to a fixed version: 4.6.10, 4.4.20.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130466 (Out-of-bounds Read in Wireshark), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130466 (entry last updated 2026-11-20):
Affected:
- Wireshark Foundation Wireshark: from 4.6.0, fixed in 4.6.10; from 4.4.0, fixed in 4.4.20
Fixed versions: 4.6.10, 4.4.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130466 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130466 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wireshark.org/security/wnpa-sec-2026-114.html
- https://gitlab.com/wireshark/wireshark/-/work_items/21635
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130466
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130466"}.Affected versions
- Wireshark Foundation WiresharkFrom 4.6.0 · fixed in 4.6.10; From 4.4.0 · fixed in 4.4.20
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.5/10CVSS 5.5
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | wireshark.org · security/wnpa-sec-2026-114.html |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130466 |
| Record | NVD · CVE-2026-130466 |
| Other links 1 | |
| Link | gitlab.com · wireshark/wireshark/-/work_items/21635 |
Questions about CVE-2026-130466
Is CVE-2026-130466 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-130466?
Wireshark: from 4.6.0 before 4.6.10; from 4.4.0 before 4.4.20.
Source: cve.now feed data
How do I fix CVE-2026-130466?
Upgrade to a fixed version: 4.6.10, 4.4.20.
Source: cve.now feed data
Related
- CVE-2026-130461NULL Pointer Dereference in Wireshark
- CVE-2026-130464Buffer Over-read in Wireshark
- CVE-2026-130469Use After Free in Wireshark
- CVE-2026-130468Heap-based Buffer Overflow in Wireshark
- CVE-2026-130463Missing Initialization of a Variable in Wireshark
- CVE-2026-130462Inefficient Algorithmic Complexity in Wireshark
No corrections so far. Something wrong on this page? Report an error.