Root access via U-Boot argument injection
Published Jun 4, 2026 · Updated Jun 4, 2026
Authentication bypass in the U-Boot component of GNCC GP5 7.1.76 allows physically proximate attackers to gain root access via UART. The unlocked UART console permits boot interruption and accepts bootargs containing init=/bin/sh, which replaces normal initialization with a root shell. Physical access to the device PCB during power-on is required, and successful exploitation grants full local control of the camera.
Summary
What happened
Authentication bypass in the U-Boot component of GNCC GP5 7.1.76 allows physically proximate attackers to gain root access via UART. The unlocked UART console permits boot interruption and accepts bootargs containing init=/bin/sh, which replaces normal initialization with a root shell. Physical access to the device PCB during power-on is required, and successful exploitation grants full local control of the camera.
The record
- CVE
- CVE-2026-36175
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-288, CWE-20, T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GNCC GP5 U-Boot Root Shell Injection PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo