Cyber Resilience

CVE-2026-4415

Path Traversal in Gigabyte Control Center ≤ 25.12.10.01

Published
30 March 2026
Modified
08 April 2026
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0065 48th percentile
Risk Priority 47 floored blend · peak EPSS

Summary

CVE-2026-4415 is a critical-severity Relative Path Traversal (CWE-23) vulnerability in Gigabyte Control Center. Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-4415 is an Arbitrary File Write vulnerability in Gigabyte Control Center, software developed by GIGABYTE. The issue arises when the pairing feature is enabled, allowing unauthenticated remote attackers to write arbitrary files to any location on the underlying operating system. This can lead to arbitrary code execution or privilege escalation. The vulnerability has a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-23 (Relative Path Traversal) and CWE-787 (Out-of-bounds Write). It was published on 2026-03-30.

Unauthenticated remote attackers can exploit this vulnerability over the network if the pairing feature is active in Gigabyte Control Center. Exploitation requires high attack complexity but no privileges or user interaction. Successful attacks enable writing files to arbitrary locations, potentially resulting in arbitrary code execution or privilege escalation on the affected system.

Advisories from TWCERT/CC detail the vulnerability and are available at https://www.twcert.org.tw/en/cp-139-10804-689cd-2.html and https://www.twcert.org.tw/tw/cp-132-10803-ae014-1.html, providing guidance on mitigation steps.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Gigabyte Control Center developed by GIGABYTE has an Arbitrary File Write vulnerability. When the pairing feature is enabled, unauthenticated remote attackers can write arbitrary files to any location on the underlying operating system, leading to arbitrary code execution or privilege…

more

escalation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2020-0986Shared CWE-787
CVE-2023-44807Shared CWE-787
CVE-2023-33635Shared CWE-787
CVE-2021-30761Shared CWE-787
CVE-2025-47725Shared CWE-787
CVE-2023-23456Shared CWE-787
CVE-2024-20067Shared CWE-787
CVE-2024-11793Shared CWE-787
CVE-2024-20103Shared CWE-787
CVE-2023-24130Shared CWE-787

Affected Assets

gigabyte
control center
≤ 25.12.10.01

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

Access enforcement directly blocks unauthorized file reads/writes that result from unresolved .. sequences.

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

Least privilege reduces the set of reachable files even when a traversal succeeds.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References