What is the CVSS score of CVE-2026-36182?

CVE-2026-36182 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of GNCC GP5 are affected by CVE-2026-36182?

GNCC GP5 IP camera firmware v7.1.76 contains a password protection weakness that enables attackers to compromise administrative credentials and gain full device control, affecting all surveillance…

How to fix or mitigate CVE-2026-36182?

24 hours: Inventory all GNCC GP5 IP cameras (v7.1.76 and earlier); restrict network access to camera management interfaces via firewall rules limiting access to authorized personnel and networks only. 7 days: Contact GNCC support for interim guidance; implement network segmentation isolating cameras from critical systems and ensure all administrative accounts use strong, unique passwords; review camera access logs for suspicious activity. 30 days: Establish patching or replacement timeline with vendor; conduct comprehensive security assessment of camera deployment; develop incident response plan for potential camera compromise.

GNCC GP5 CVE-2026-36182

EUVD-2026-34309 CRITICAL

Use of Weak Hash (CWE-328)

2026-06-04 mitre

GHSA-q39m-5r2m-g8v4

Information Disclosure N A

9.8

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (mitre) · only source for this CVE.

CVSS VectorVendor: mitre

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 15:37 vuln.today

CVSS changed

Jun 08, 2026 - 15:37 NVD

9.8 (CRITICAL)

CVE Published

Jun 04, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

GNCC GP5 v7.1.76 was discovered to utilize a weak hashing algorithm to protect the root password, possibly allowing attackers to obtain root credentials and privileges via a bruteforce attack.

AnalysisAI

Weak password hashing on the GNCC GP5 IP camera (firmware v7.1.76) allows attackers who obtain the password hash to recover the root credential via offline brute-force, yielding full device takeover. The CVSS 9.8 score reflects network-reachable impact, but real-world exploitation first requires extracting the hash from the device; no public exploit identified at time of analysis and EPSS is very low at 0.02%.

Technical ContextAI

The GNCC GP5 is a consumer IoT/IP camera whose Linux-based firmware stores the root account credential using a cryptographically weak hashing algorithm (CWE-328: Use of Weak Hash). Such embedded devices typically store credentials in /etc/passwd or /etc/shadow, and weak algorithms like DES crypt or unsalted MD5 are highly susceptible to GPU-accelerated brute-force or rainbow-table attacks. Once root credentials are recovered they can be reused across telnet, SSH, the web management interface, or any debug service the firmware exposes, giving attackers complete control of the embedded Linux environment. The CPE field is unpopulated (cpe:2.3:a:n/a:n/a:*) so the affected product set is not formally enumerated in NVD beyond the vendor research report.

RemediationAI

No vendor-released patch identified at time of analysis; GNCC has not published a firmware update addressing the weak hash for the GP5 at v7.1.76. Until a fix ships, owners should change the root password to a long, high-entropy passphrase (raising brute-force cost even against a weak algorithm), isolate the camera on a segmented IoT VLAN with no inbound internet exposure (trade-off: remote viewing via the vendor cloud may still work but direct admin access from the WAN is blocked), and disable any unused services such as telnet/SSH/UART if the firmware menu allows it (trade-off: loss of remote troubleshooting). Monitor the vendor sites http://gncc.com and http://gp5.com for firmware updates and the researcher's GitHub page at https://github.com/BadChemical/IoT-Vulnerability-Research-Public for any disclosed mitigations, and review the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-36182 for updates.