# CVE-2025-10568: HyperX NGENUITY - Arbitrary Code Execution

> An attacker can execute arbitrary code on systems running HyperX NGENUITY software due to a command injection vulnerability.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-83hp-pfwm-9wm3

## What is CVE-2025-10568?

CVE-2025-10568 is a medium-severity command injection vulnerability in HP Inc. HyperX NGENUITY, published on 19 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

HyperX NGENUITY software is potentially vulnerable to arbitrary code execution. HP is releasing updated software to address the potential vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-10568?

It affects 1 product.


Products: Hyperx Ngenuity.

## How do I fix CVE-2025-10568?

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

## Is CVE-2025-10568 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10568 and fix it if it is affected.

What it is: CVE-2025-10568 is a medium-severity command injection vulnerability in HP Inc. HyperX NGENUITY, published on 19 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-10568 in the wild and no public exploit code.

Affected product: HP Inc. HyperX NGENUITY. 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-2025-10568/ (Markdown: https://insights.sbomify.com/CVE-2025-10568/index.md)
```

## Sources

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

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