System-file modification via bind-mount integrity bypass
Published Jun 4, 2026 · Updated Jun 4, 2026
Improper access control in GNCC GP5 firmware 7.1.76 allows physically proximate attackers to modify system files via bind mounts. The firmware uses runtime overlays for its Squashfs system image without enforcing integrity when a bind mount replaces a protected path. Physical access and a root shell obtained through the exposed UART boot path are required; modifications affect files and binaries only until reboot.
Summary
What happened
Improper access control in GNCC GP5 firmware 7.1.76 allows physically proximate attackers to modify system files via bind mounts. The firmware uses runtime overlays for its Squashfs system image without enforcing integrity when a bind mount replaces a protected path. Physical access and a root shell obtained through the exposed UART boot path are required; modifications affect files and binaries only until reboot.
The record
- CVE
- CVE-2026-36180
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1685
- Attack vector
- physical
- Privileges
- admin
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.
Public exploit references
- GNCC GP5 hardware-to-cloud proof of conceptproof of concept · unverified
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