# CVE-2026-86330: Noobaa-core: noobaa-core: os command injection in cluster_internal_api.set_hostname_internal

> An authenticated administrator can execute arbitrary OS commands via the hostname parameter in NooBaa's internal API, compromising the host system.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-xc7x-4vw8-2652

## What is CVE-2026-86330?

CVE-2026-86330 is a high-severity command injection vulnerability in Red Hat Openshift Data Foundation 4, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An OS command injection flaw was found in the set_hostname_internal function of NooBaa's cluster_internal_api. This component is responsible for managing the Multi-Cloud Object Gateway in OpenShift Data Foundation. The vulnerability occurs because the hostname parameter is passed directly to a shell command without proper sanitization. An authenticated attacker with administrative privileges can provide a specially crafted hostname containing shell metacharacters to execute arbitrary commands on the host system with the privileges of the NooBaa process.

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

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


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

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

## Is CVE-2026-86330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86330 is a high-severity command injection vulnerability in Red Hat Openshift Data Foundation 4, published on 28 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86330 in the wild and no public exploit code.

Affected product: Red Hat Openshift Data Foundation 4. 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-86330/ (Markdown: https://insights.sbomify.com/CVE-2026-86330/index.md)
```

## Sources

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

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