# CVE-2026-90621: ipa-lab HackingBuddyGPT ssh_run_command.py ssh_run_command os command injection

> Remote attackers can execute arbitrary OS commands via the ssh_run_command function in HackingBuddyGPT, posing a risk to users of this security testing tool.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-34ch-x498-hrhv

## What is CVE-2026-90621?

CVE-2026-90621 is a medium-severity command injection vulnerability in ipa-lab HackingBuddyGPT, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in ipa-lab HackingBuddyGPT up to 0.5.0. This affects the function ssh_run_command of the file src/hackingBuddyGPT/extensions/ssh_run_command.py. Such manipulation leads to os command injection. The attack can be launched remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-90621 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90621 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90621 is a medium-severity command injection vulnerability in ipa-lab HackingBuddyGPT, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90621 exists.

Affected product: ipa-lab HackingBuddyGPT. 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-90621/ (Markdown: https://insights.sbomify.com/CVE-2026-90621/index.md)
```

## Sources

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

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