# CVE-2026-4415: GIGABYTE｜Gigabyte Control Center - Arbitrary File Write

> Unauthenticated attackers can write arbitrary files via the pairing feature, leading to code execution or privilege escalation.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-hvj3-h37v-8xmq

## What is CVE-2026-4415?

CVE-2026-4415 is a critical path traversal vulnerability in Gigabyte Control Center, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 escalation.

Weakness: CWE-787 (Out-of-bounds Write), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-4415?

It affects 1 product.


Products: Gigabyte Control Center.

## How do I fix CVE-2026-4415?

No fix has been published for CVE-2026-4415 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4415 being exploited?

There is no known exploitation of CVE-2026-4415 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4415 and fix it if it is affected.

What it is: CVE-2026-4415 is a critical path traversal vulnerability in Gigabyte Control Center, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4415 in the wild and no public exploit code.

Affected product: Gigabyte Control Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4415/ (Markdown: https://insights.sbomify.com/CVE-2026-4415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4415
- OSV: https://osv.dev/vulnerability/CVE-2026-4415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4415/
Summaries are generated and may contain mistakes; the official description above is the record.