# CVE-2026-66733: Sonic 3 A.I.R. Unbounded Memory Allocation DoS via ReceivedPacketCache

> Unauthenticated remote attackers can crash the Sonic 3 A.I.R. server by sending crafted UDP packets that trigger unbounded memory allocation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-947v-gcqq-82hv

## What is CVE-2026-66733?

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

### Official description

Sonic 3 A.I.R. before commit 2492d18 contains an unbounded memory allocation vulnerability in ReceivedPacketCache::enqueuePacket() that allows unauthenticated remote attackers to crash the server process by sending a crafted UDP packet with mUniquePacketID set to the maximum uint32 value. The mUniquePacketID field is read directly from the UDP wire-format packet header without bounds checking, causing the server to allocate one CacheItem per missing packet ID gap, exhausting available host memory and propagating an uncaught std::bad_alloc exception to std::terminate().

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

No fix has been published for CVE-2026-66733 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-66733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66733 is a high-severity denial of service vulnerability in Eukaryot sonic3air, published on 6 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-66733 in the wild and no public exploit code.

Affected product: Eukaryot sonic3air. 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-66733/ (Markdown: https://insights.sbomify.com/CVE-2026-66733/index.md)
```

## Sources

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

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