CVE-2026-36176
HighCVSS 7.1Exploitation Probability (EPSS)
Low risk1th percentile - higher than 1% of all known CVEs
Summary
GNCC GP5 v7.1.76 stores pre-signed Backblaze B2 upload URLs (PUT requests) in plaintext to the serial console. Physically-proximate attackers can extract these active tokens to perform unauthorized operations via monitoring the serial UART interface.
Risk Assessment
Risk of leakage of active authentication tokens to Backblaze B2, potentially allowing an attacker unauthorized access to cloud data.
Recommendation
It is recommended to update GNCC GP5 firmware to a version that does not store tokens in plaintext, or secure access to the serial console.
Other vulnerabilities in GNCC GP5
See all- CVE-2026-36182Critical
GNCC GP5 v7.1.76 uses a weak hashing algorithm to protect the root password. Attackers can perform a brute-force attack to obtain root credentials and escalate privileges.
- CVE-2026-36180Medium
A lack of runtime integrity in GNCC GP5 v7.1.76 allows physically-proximate attackers to bypass file system read-only protections and modify system files and binaries for the duration of a boot session via a bind-mount attack.
- CVE-2026-36178Medium
The factory reset functionality in GNCC GP5 v7.1.76 fails to clear sensitive cryptographic material in the JFFS2 configuration partition, possibly allowing attackers to recover and obtain sensitive user data.
- CVE-2026-36174Medium
GNCC GP5 v7.1.76 stores sensitive wireless network information in plaintext during routine operations to the serial console, allowing physically-proximate attackers to obtain sensitive information, including network credentials, via monitoring the serial UART interface.
Original NVD description (English source)
GNCC GP5 v7.1.76 was discovered to store pre-signed Backblaze B2 upload URLs (PUT requests) in plaintext to the serial console. This allows physically-proximate attackers to extract these active tokens to perform unauthorized operations via monitoring the serial UART interface.