Is CVE-2026-36182 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-36182 being exploited in the wild.

How severe is CVE-2026-36182?

Informational severity, published 4 June 2026.

Is there a fix for CVE-2026-36182?

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-36182 attacked?

It is attacked with local access or over the network, in a network appliance.

Am I affected by CVE-2026-36182?

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.

CVE-2026-36182: GNCC GP5 weak password hashing for root account

CVE-2026-36182 · Severity: info · Published 2026-06-04

The GNCC GP5, an IoT device, uses an outdated and weak method for securing its administrative root password. This flaw makes it significantly easier for an unauthorized person to guess the password through automated 'brute-force' attempts. If successful, an attacker would gain full control over the device, potentially allowing them to intercept data, disrupt operations, or use the device as a foothold to attack other parts of the network.

Technologies: GNCC GP5. Vendors: GNCC.

Quick answers

Is CVE-2026-36182 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-36182 being exploited in the wild.
How severe is CVE-2026-36182?: Informational severity, published 4 June 2026.
Which products and versions are affected?: GNCC GP5 v7.1.76.
Is there a fix for CVE-2026-36182?: 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-36182 attacked?: It is attacked with local access or over the network, in a network appliance.
Am I affected by CVE-2026-36182?: 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 version v7.1.76 is vulnerable to credential recovery due to the use of a weak cryptographic hashing algorithm for protecting the root password. This implementation flaw allows an attacker with access to the password hashes (potentially via local file access or other configuration exports) to perform offline brute-force or rainbow table attacks with high efficiency. Successful exploitation results in the recovery of the plaintext root credentials, granting the attacker full administrative privileges over the IoT device. No specific patch has been confirmed in the advisory, though users should monitor for firmware updates beyond v7.1.76.

Affected products

GNCC GP5 v7.1.76

Timeline

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

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.