Eukaryot Sonic3air up to 26.03.28.0 ReceivedPacketCache enqueuePacket mUniquePacketID allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 2.85 |
Summary
A vulnerability marked as problematic has been reported in Eukaryot Sonic3air up to 26.03.28.0. This vulnerability affects the function ReceivedPacketCache::enqueuePacket of the component ReceivedPacketCache. Performing a manipulation of the argument mUniquePacketID results in allocation of resources.
This vulnerability is known as CVE-2026-66733. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Eukaryot Sonic3air up to 26.03.28.0. It has been classified as problematic. This affects the function ReceivedPacketCache::enqueuePacket of the component ReceivedPacketCache. The manipulation of the argument mUniquePacketID with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:
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().
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-66733 since 07/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying the patch 2492d1882cd2cf1cc1d7415729ce5c4fd686cd4f is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-53876). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 26.03.0
- 26.03.1
- 26.03.2
- 26.03.3
- 26.03.4
- 26.03.5
- 26.03.6
- 26.03.7
- 26.03.8
- 26.03.9
- 26.03.10
- 26.03.11
- 26.03.12
- 26.03.13
- 26.03.14
- 26.03.15
- 26.03.16
- 26.03.17
- 26.03.18
- 26.03.19
- 26.03.20
- 26.03.21
- 26.03.22
- 26.03.23
- 26.03.24
- 26.03.25
- 26.03.26
- 26.03.27
- 26.03.28.0
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 2492d1882cd2cf1cc1d7415729ce5c4fd686cd4f
Timeline
07/27/2026 CVE reserved08/06/2026 Advisory disclosed
08/06/2026 VulDB entry created
08/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-66733 (🔒)
GCVE (CVE): GCVE-0-2026-66733
GCVE (VulDB): GCVE-100-386565
EUVD: 🔒
Entry
Created: 08/06/2026 15:23Updated: 08/06/2026 16:34
Changes: 08/06/2026 15:23 (57), 08/06/2026 16:34 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.