CVE-2026-36182
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGNCC 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGNCC GP5 v7.1.76 stores the root password using a weak hashing algorithm that provides insufficient protection against brute-force attacks, potentially allowing unauthenticated attackers to recover plaintext root credentials and gain full system access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device CLI, web interface, or system information page and locate the model (GNCC GP5) and firmware version number. On most embedded devices, this is shown in the web UI under 'System Information' or via CLI command like 'show version' or 'version'.Affected if The device is GNCC GP5 running firmware version 7.1.76 or potentially earlier versions using the same codebase.
-
Locate the password hash storage fileAccess the device filesystem via UART, JTAG, or by extracting the firmware binary. Look for shadow or passwd files typically found in /etc/shadow, /etc/passwd, or configuration files under /etc/config/ on embedded Linux systems.Affected if Password hash files exist on the device filesystem and are readable or extractable by an attacker.
-
Extract root password hashOpen the identified password file using a text editor or command line tool (cat, less). Locate the entry for the root user account.Affected if A root user account exists with a stored password hash in the system.
-
Analyze the hashing algorithm usedExamine the password hash format. MD5 hashes appear as $1$... (31 characters), DES as 13 characters starting with no prefix, or look for identifiers like $1$ (MD5), $5$ (SHA-256), $6$ (SHA-512). Compare hash format against known weak algorithm patterns.Affected if The root password hash uses MD5 ($1$), DES, or another crypt(3) legacy algorithm rather than modern salted hashes like bcrypt ($2a$), scrypt ($scrypt$), or Argon2.
-
Verify hash is vulnerable to offline brute-forceAttempt to crack the extracted hash using hashcat or john the ripper with a wordlist. If the password is recovered in a reasonable time, the algorithm is confirmed weak.Affected if The password hash can be successfully cracked using standard GPU-based tools within hours or days, confirming the use of a weak hashing algorithm.
The environment is affected if the device is GNCC GP5 firmware v7.1.76 (or similar) and the root password hash in /etc/shadow or equivalent uses a legacy algorithm like MD5 or DES rather than bcrypt, scrypt, or Argon2.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the weak password hashing algorithm with a modern, computationally expensive algorithm such as bcrypt, scrypt, or Argon2, and migrate existing password hashes to the new format.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data