# CVE-2026-65819: Denial of service in gopacket

> Attackers can cause a denial of service by sending crafted packets that trigger panics in gopacket layer decoders due to unchecked bounds.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** AZL-95490, DEBIAN-CVE-2026-65819, GHSA-8mcr-459q-5mx2, UBUNTU-CVE-2026-65819

## What is CVE-2026-65819?

CVE-2026-65819 is a high-severity denial of service vulnerability in gopacket, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-65819?


## How do I fix CVE-2026-65819?

Apply the vendor's patch.

## Is CVE-2026-65819 being exploited?

There is no known exploitation of CVE-2026-65819 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65819 and fix it if it is affected.

What it is: CVE-2026-65819 is a high-severity denial of service vulnerability in gopacket, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65819 in the wild and no public exploit code.

Affected product: gopacket. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65819/ (Markdown: https://insights.sbomify.com/CVE-2026-65819/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65819
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65819
- OSV: https://osv.dev/vulnerability/CVE-2026-65819

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65819/
Summaries are generated and may contain mistakes; the official description above is the record.