# CVE-2026-30308: Command injection in n/a

> Prompt injection allows attackers to bypass safety checks and execute arbitrary commands in HAI Build Code Generator.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 Apr 2026
- **Also known as:** GHSA-gr6f-xx69-hrgq

## What is CVE-2026-30308?

CVE-2026-30308 is a critical command injection vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In its design for automatic terminal command execution, HAI Build Code Generator offers two options: Execute safe commands and Execute all commands. The description for the former states that commands determined by the model to be safe will be automatically executed, whereas if the model judges a command to be potentially destructive, it still requires user approval. However, this design is highly susceptible to prompt injection attacks. An attacker can employ a generic template to wrap any malicious command and mislead the model into misclassifying it as a 'safe' command, thereby bypassing the user approval requirement and resulting in arbitrary command execution.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Presidio Hai Build.

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

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

## Is CVE-2026-30308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30308 is a critical command injection vulnerability in n/a, 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-30308 in the wild and no public exploit code.

Affected product: n/a. 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-30308/ (Markdown: https://insights.sbomify.com/CVE-2026-30308/index.md)
```

## Sources

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

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