SGUDA U-Lock - Broken Access Control
Priority MEDIUM 41CWE-863Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
SGUDA U-Lock central lock control service’s lock management function has incorrect authorization. A remote attacker with general privilege can exploit this vulnerability to call privileged APIs to acquire information, manipulate or disrupt the functionality of arbitrary electronic locks.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00734 54th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| SGUDA | U-Lock | — | — | No fix listed | CNA |
- U-Lock VendorSGUDA Affected — Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2022-46307
- 2026-10-03 Alias added: GHSA-c4m9-c23m-m88f
References
More SGUDA U-lock Firmware vulnerabilities
- TI-2022-22855 SGUDA U-Lock - Broken Access Control CVSS 3.1HIGH 8.8
Sources
- CVE-2022-46307 · CVE Program
- CVE-2022-46307 · NVD
- FIRST EPSS
- GHSA-c4m9-c23m-m88f · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences