CVE-2026-36175
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 · uneditedAn issue in the U-Boot component of GNCC GP5 v7.1.76 allows physically-proximate attackers to bypass authentication and gain root access via interrupting the boot sequence and injecting a crafted string into the kernel boot arguments.
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 confidenceThe vulnerability exists in the U-Boot bootloader of GNCC GP5 v7.1.76, where physically proximate attackers can interrupt the boot sequence and inject crafted strings into kernel boot arguments, bypassing authentication to gain root 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 the device modelCheck the product model of the device (look for GNCC GP5 labeling, FCC ID, or system information)Affected if The device is a GNCC GP5 unit
-
Check U-Boot bootloader versionAccess the bootloader console (typically via serial connection during boot) and look for version information displayed during the boot sequenceAffected if The U-Boot version displays as v7.1.76 or if version information is unavailable but the device is GNCC GP5
-
Verify bootloader password protection statusDuring boot, press the key to interrupt the boot sequence (commonly Space, Enter, or a function key). Observe whether a password prompt appears before accessing the U-Boot consoleAffected if No password is required to access the U-Boot console and modify boot arguments
-
Check for console interrupt protectionObserve whether pressing any key during the boot process interrupts the automatic boot and enters the bootloader interactive modeAffected if The boot sequence can be interrupted by pressing a key without authentication
-
Inspect boot argument configurationAt the U-Boot prompt (if accessible), run 'printenv' or 'bootargs' to view current kernel boot parametersAffected if Boot arguments can be modified without restriction or authentication
If the device is a GNCC GP5 with U-Boot v7.1.76 and the bootloader console can be accessed without a password to modify boot arguments, the environment is affected by this vulnerability.
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 dataApply U-Boot security patches or upgrade to a hardened bootloader version that validates boot arguments and implements authenticated boot verification to prevent arbitrary kernel parameter injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36175 — 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-36175 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