CVE-2026-65819

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (49th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 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.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

gopacket provides packet processing capabilities for Go. Through version 1.7.0, multiple layer decoders use attacker-controlled lengths, counts, or offsets before validating them against packet buffers, allowing a crafted packet decoded through DecodingLayerParser or DecodeFromBytes to trigger an unrecovered panic and remotely deny service. A patch commit is available at 210f25f.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v1.7.0

Patch available: gopacket/gopacket v1.7.0

https://github.com/gopacket/gopacket/releases/tag/v1.7.0
github_commit

commit 210f25fb9b3c (gopacket/gopacket)

Fix landed in gopacket/gopacket commit 210f25fb9b3c — awaiting tagged release

https://github.com/gopacket/gopacket/commit/210f25fb9b3ca1af2eb649936f78ad6991b6c9c5
github Patch Available

Multiple layer decoders panic on crafted packets (out-of-bounds/underflow) enabling unauthenticated remote DoS via DecodingLayerParser · Advisory · gopacket/gopacket · GitHub

https://github.com/gopacket/gopacket/security/advisories/GHSA-8mcr-459q-5mx2

Vendor Advisories for CVE-2026-65819(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnetwork-observability/network-observability-cli-rhel9:17899862792026-09-23redhat

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

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.0.0-1, 1.2.0-1, 1.2.0-2, 1.3.0-1, 1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-3 ... 1.1.19-6.2 (6 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-6.2
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-6.2
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gopacket1.1.19-1 ... 1.1.19-6.2 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 83× 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.

Showing the most recent 100 of 156 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Debian:11:gopacket

Frequently asked(5)

What is CVE-2026-65819?
CVE-2026-65819 is a high vulnerability published on August 7, 2026. gopacket provides packet processing capabilities for Go. Through version 1.7.0, multiple layer decoders use attacker-controlled lengths, counts, or offsets before validating them against packet buffers, allowing a crafted packet decoded through DecodingLayerParser or DecodeFromBytes to trigger an…
When was CVE-2026-65819 disclosed?
CVE-2026-65819 was first published on August 7, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65819 actively exploited?
CVE-2026-65819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65819?
CVE-2026-65819 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65819?
A fix for CVE-2026-65819 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65819 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65819?

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

Book a Demo →Browse All CVEs