CVE-2026-3203

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

RF4CE Profile protocol dissector crash in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

February 25, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Wireshark • Go Deep | Wireshark • wnpa-sec-2026-07 RF4CE Profile dissector crash

https://www.wireshark.org/security/wnpa-sec-2026-07.html
generic

Fuzz job crash: fuzz-2026-02-06-13021968622.pcap (#21009) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/issues/21009

Vendor Advisories for CVE-2026-3203(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatwireshark-1:4.4.2-3.el10_0.42026-06-16redhat
redhatwireshark-1:4.4.2-4.el10_1.42026-04-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wireshark3.4.10-0+deb11u1 ... 4.6.6-2 (69 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wireshark4.0.10-1 ... 4.6.6-2 (50 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wireshark4.4.13-0+deb13u1, 4.4.7-1, 4.4.8-0exp1, 4.4.9-14.4.14-0+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wireshark4.4.7-1 ... 4.6.3-1 (12 versions)4.6.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-17 18:55 UTCEG score recompute
  5. 2026-09-17 18:55 UTCVendor advisory
  6. 2026-09-17 18:54 UTCGHSA enrichment
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:11 UTCEPSS rescore
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 15:01 UTCEPSS rescore
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 09:37 UTCEPSS rescore
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-08 22:00 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-04 05:06 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:53 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-31 16:34 UTCOSV refresh
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:41 UTCEPSS rescore
Show 67 more
  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 21:13 UTCVendor advisory
  13. 2026-08-14 21:13 UTCGHSA enrichment
  14. 2026-08-14 09:01 UTCEG score recompute
  15. 2026-08-14 09:01 UTCVendor advisory
  16. 2026-08-14 09:01 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 01:01 UTCEG score recompute
  19. 2026-08-13 01:01 UTCVendor advisory
  20. 2026-08-13 01:01 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 23:58 UTCEG score recompute
  23. 2026-08-11 23:58 UTCVendor advisory
  24. 2026-08-11 23:58 UTCGHSA enrichment
  25. 2026-08-11 13:43 UTCEPSS rescore
  26. 2026-08-11 06:23 UTCEG score recompute
  27. 2026-08-11 06:23 UTCVendor advisory
  28. 2026-08-11 06:23 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 08:48 UTCVendor advisory
  31. 2026-08-10 08:48 UTCGHSA enrichment
  32. 2026-08-09 19:36 UTCEG score recompute
  33. 2026-08-09 19:36 UTCVendor advisory
  34. 2026-08-09 19:36 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 08:40 UTCEG score recompute
  37. 2026-08-09 08:40 UTCVendor advisory
  38. 2026-08-09 08:40 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 07:40 UTCVendor advisory
  41. 2026-08-08 07:40 UTCGHSA enrichment
  42. 2026-08-07 20:44 UTCEG score recompute
  43. 2026-08-07 20:44 UTCVendor advisory
  44. 2026-08-07 20:44 UTCGHSA enrichment
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-06 03:01 UTCEG score recompute
  47. 2026-08-06 03:01 UTCVendor advisory
  48. 2026-08-06 03:01 UTCGHSA enrichment
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:38 UTCEPSS rescore
  52. 2026-08-04 05:53 UTCEG score recompute
  53. 2026-08-04 05:53 UTCVendor advisory
  54. 2026-08-04 05:53 UTCGHSA enrichment
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 19:35 UTCEG score recompute 2.00
  57. 2026-08-02 19:35 UTCVendor advisory
  58. 2026-08-02 19:35 UTCGHSA enrichment
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-27 14:13 UTCEPSS rescore
  64. 2026-07-27 12:55 UTCEG score recompute
  65. 2026-07-27 12:55 UTCVendor advisory
  66. 2026-07-27 12:55 UTCGHSA enrichment
  67. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-3203?
CVE-2026-3203 is a high vulnerability published on February 25, 2026. RF4CE Profile protocol dissector crash in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service
When was CVE-2026-3203 disclosed?
CVE-2026-3203 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3203 actively exploited?
CVE-2026-3203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.7% of all scored CVEs.
What is the CVSS score of CVE-2026-3203?
CVE-2026-3203 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-3203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3203, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3203

Explore →

Is Your Infrastructure Affected by CVE-2026-3203?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.