Unitree UPK
Unitree UPK files Hard-Coded Key
Edge device · Device firmwarehardware or firmware CPE: unitree go1_air_firmware (medium confidence)
Since the encryption algorithm used to protect firmware updates is itself encrypted using key material available to an attacker (or anyone paying attention), the firmware updates may be altered by an unauthorized user, and then trusted by a Unitree product, such as the Unitree Go2 and other models. This issue appears to affect all of Unitree’s current offerings as of February 26, 2026, and so should be considered a vulnerability in both the firmware generation and extraction processes. At the time of this release, there is no publicly-documented mechanism to subvert the update process and insert poisoned firmware packages without the equipment owner’s knowledge.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 20260226v1
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationPublic PoC known, its date not yet looked up; not in CISA KEV.
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Bin4ry/UniTEABag | 15 Jan 2026 −43 d | 32 | PoC older repo: PoC date unknown, not used for the first PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.