Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Wireshark Foundation Wireshark 4.4.15, 4.6.5.
- Severity is disputed: the assigning authority (CNA) scores it 5.5, NVD 7.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Wireshark Foundation Wireshark 4.4.15, 4.6.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
UDS protocol dissector infinite loop in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service
- Published
- Apr 30, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-835
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitLab
- 5.5
- 2.0 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wireshark | wireshark | cpe:2.3:a:wireshark:wireshark |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wireshark wireshark4.4.0 and later · before 4.4.15
- wireshark wireshark4.6.0 and later · before 4.6.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.
Wireshark Foundation Wireshark
- 4.6.0 and later · before 4.6.5affected · semver
- 4.4.0 and later · before 4.4.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | wireshark | from 0 | — |
| Debian:13 | wireshark | before 4.4.15-0+deb13u1 | 4.4.15-0+deb13u1 |
| Debian:14 | wireshark | before 4.6.5-1 | 4.6.5-1 |
| openSUSE:Leap 16.0 | wireshark | before 4.4.17-160000.1.1 | 4.4.17-160000.1.1 |
| SUSE:Linux Enterprise Server 16.0 | wireshark | before 4.4.17-160000.1.1 | 4.4.17-160000.1.1 |
Same product
wireshark: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-0304Multiple buffer overflows in the LWRES dissector in Wireshark 0.9.15 through 1.0.10 and 1.2.0 through 1.2.5 allow remote attackers to cause 52Plan
- CVE-2014-2299Buffer overflow in the mpeg_read function in wiretap/mpeg.c in the MPEG parser in Wireshark 1.8.x before 1.8.13 and 1.10.x before 1.10.6 all51Plan
- CVE-2011-1591Stack-based buffer overflow in the DECT dissector in epan/dissectors/packet-dect.c in Wireshark 1.4.x before 1.4.5 allows remote attackers t50Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-3203Feb 25, 2026 · Buffer Over-read in Wireshark30Monitor
- ← EarlierCVE-2026-6868Apr 30, 2026 · Stack-based Buffer Overflow in Wireshark30Monitor
- Later →CVE-2026-7376Apr 30, 2026 · NULL Pointer Dereference in Wireshark30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Wireshark Foundation Wireshark | 4.4.15 | Vendor (CNA) |
| Wireshark Foundation Wireshark | 4.6.5 | Vendor (CNA) |
| debian:wireshark | 4.4.15-0+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:wireshark | 4.4.17-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:wireshark | 4.4.17-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jaime Caverofinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-65190 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark30Monitor
- CVE-2026-65200 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark30Monitor
- CVE-2026-1516369 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark30Monitor
- CVE-2026-65310 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark22Monitor
- CVE-2026-65340 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark22Monitor
- CVE-2026-65360 days apartLoop with Unreachable Exit Condition ('Infinite Loop') in Wireshark22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0134 · Apr 30, 2026(Wireshark Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.