Quick answers
- Is CVE-2026-36176 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-36176 being exploited in the wild.
- How severe is CVE-2026-36176?
- Informational severity, with a CVSS score of 0, published 4 June 2026.
- Which products and versions are affected?
- GNCC GP5 v7.1.76.
- Is there a fix for CVE-2026-36176?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-36176 attacked?
- It is attacked with physical access, in a network appliance.
- Am I affected by CVE-2026-36176?
- Check whether you run GNCC GP5 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
GNCC GP5 firmware version v7.1.76 contains an information disclosure vulnerability where pre-signed Backblaze B2 upload URLs (used for PUT requests) are logged in plaintext to the serial UART interface. An attacker with physical access to the device's internal hardware can monitor the serial console during operation to extract these active authentication tokens. Once captured, these tokens can be used to perform unauthorized file operations against the associated Backblaze B2 bucket. The attack requires physical proximity and hardware-level monitoring of the UART pins.
Affected products
- GNCC GP5 v7.1.76
Timeline
- 2026-06-04: disclosed: Initial disclosure via MITRE and NVD
- 2026-06-04: advisory