CVE-2026-36180
Deferred Deferred - Pending Action
Runtime Integrity Bypass in GNCC GP5 v7.1.76

Publication date: 2026-06-04

Last updated on: 2026-06-08

Assigner: MITRE

Description
A lack of runtime integrity in GNCC GP5 v7.1.76 allows physically-proximate attackers to bypass file system read-only protections and modify system files and binaries for the duration of a boot session via a bind-mount attack.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-04
Last Modified
2026-06-08
Generated
2026-06-25
AI Q&A
2026-06-05
EPSS Evaluated
2026-06-23
NVD
CVE-2026-36180
EUVD
EUVD-2026-34281
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
gncc gp5 7.1.76
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Executive Summary

This vulnerability is a lack of runtime integrity in GNCC GP5 version 7.1.76. It allows attackers who are physically close to the device to bypass the file system's read-only protections. They can do this by using a bind-mount attack to modify system files and binaries during the current boot session.

Impact Analysis

The impact of this vulnerability is that an attacker with physical proximity can alter critical system files and binaries temporarily. This could compromise the integrity and security of the system during the boot session, potentially allowing unauthorized actions or system manipulation.

Mitigation Strategies

To mitigate the vulnerability in GNCC GP5 v7.1.76, immediate steps include restricting physical access to the device to prevent physically-proximate attackers from performing bind-mount attacks.

Since the vulnerability allows modification of system files and binaries during a boot session, ensuring the device is in a secure environment and monitoring for unauthorized physical access is critical.

No specific patches or software mitigations are mentioned, so physical security and limiting device exposure are the primary defenses.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-36180. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart