# CVE-2026-36178: GNCC GP5 improper data sanitization in factory reset

Source: https://junglewise.ai/threats/cve-2026-36178-gncc-gp5-improper-data-sanitization-in-factory-reset  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-04. Updated: 2026-06-04  
License: CC BY 4.0 with a link back

CVE-2026-36178 · Severity: info · CVSS 0 · Published 2026-06-04

The GNCC GP5 smart camera fails to properly erase sensitive data during a factory reset. This means that if a device is sold, returned, or discarded, a new owner with physical access could potentially recover the previous user's cryptographic keys and private information. This flaw undermines the privacy and security expectations of users who believe their data has been wiped.

Technologies: [GNCC GP5](https://junglewise.ai/threats/technologies/gp5). Vendors: [GNCC](https://junglewise.ai/threats/vendors/gncc).

## Quick answers

**Is CVE-2026-36178 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-36178 being exploited in the wild.

**How severe is CVE-2026-36178?** 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-36178?** 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-36178 attacked?** It is attacked with physical access, in a network appliance.

**Am I affected by CVE-2026-36178?** 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

The GNCC GP5 (v7.1.76) contains a flaw in its factory reset implementation where sensitive cryptographic material is not purged from the JFFS2 configuration partition. An attacker with physical access to the device can extract the flash memory or access the file system to recover these persistent secrets. This vulnerability stems from incomplete data sanitization during the reset routine. Successful exploitation allows for the recovery of sensitive user data or credentials that were intended to be deleted. No patch is currently specified in the advisory.

## Affected products

- GNCC GP5 v7.1.76

## Timeline

- 2026-06-04: disclosed: Initial disclosure via MITRE and NVD
- 2026-06-04: advisory

## References

- [http://gncc.com/](http://gncc.com/)
- [http://gp5.com/](http://gp5.com/)
- [https://github.com/BadChemical/IoT-Vulnerability-Research-Public/blob/main/GNCC-GP5-T23/README.md](https://github.com/BadChemical/IoT-Vulnerability-Research-Public/blob/main/GNCC-GP5-T23/README.md)

## Related threats

- [GNCC GP5 weak password hashing for root account](https://junglewise.ai/threats/cve-2026-36182-gncc-gp5-weak-password-hashing-for-root-account)
- [GNCC GP5 file system integrity bypass via bind-mount attack](https://junglewise.ai/threats/cve-2026-36180-gncc-gp5-file-system-integrity-bypass-via-bind-mount-attack)
- [GNCC GP5 plaintext token disclosure in serial console](https://junglewise.ai/threats/cve-2026-36176-gncc-gp5-plaintext-token-disclosure-in-serial-console)
- [GNCC GP5 authentication bypass in U-Boot](https://junglewise.ai/threats/cve-2026-36175-gncc-gp5-authentication-bypass-in-u-boot)
- [GNCC GP5 plaintext information disclosure in serial console](https://junglewise.ai/threats/cve-2026-36174-gncc-gp5-plaintext-information-disclosure-in-serial-console)