# Galaxy NG: command injection vulnerability

Advisory record · `GHSA-6hw7-j4jw-wpff`

- **Identifiers:** `GHSA-6hw7-j4jw-wpff` · `CVE-2026-12398` · `PYSEC-2026-2486`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md)
- **Published:** 16 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Jun 2026, 15:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `galaxy-ng` (PyPI): affected `<=4.9.2`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Galaxy NG (galaxy-ng, PyPI package) versions up to and including 4.9.2 are affected by a command injection flaw in the legacy role import API (v1). Git branch or tag names are passed unsanitized into shell commands, so an authenticated user who controls a git repository can run commands on the Pulp worker. The vulnerable endpoint is only reachable when GALAXY_ENABLE_LEGACY_ROLES is set to True, which is not the default. No fixed version is listed; disabling that setting removes the exposed endpoint.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0089, the 59th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 16 Jun 2026, 14:52 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-12398)
- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6hw7-j4jw-wpff)

## Sources

- [GitHub Advisory Database: GHSA-6hw7-j4jw-wpff](https://github.com/advisories/GHSA-6hw7-j4jw-wpff)
- [OSV: GHSA-6hw7-j4jw-wpff](https://osv.dev/vulnerability/GHSA-6hw7-j4jw-wpff)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-12398>
- <https://access.redhat.com/security/cve/CVE-2026-12398>
- <https://bugzilla.redhat.com/show_bug.cgi?id=2489180>
- <https://github.com/ansible/galaxy_ng>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6hw7-j4jw-wpff>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6hw7-j4jw-wpff/>. Everything for agents: <https://agentprime.io/llms.txt>.