# CVE-2025-31951: HCL BigFix RunBookAI is affected by a Unvalidated Command Input / Potential Command Smuggling vulnerability

> An attacker can execute unauthorized commands due to unvalidated input in HCL BigFix RunBookAI, potentially compromising the system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-w9jr-wh7w-mh6j

## What is CVE-2025-31951?

CVE-2025-31951 is a high-severity command injection vulnerability in HCL BigFix RunBookAI, published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL BigFix RunBookAI is affected by a Unvalidated Command Input / Potential Command Smuggling vulnerability. A flaw in a component's input handling was identified that could permit unauthorized command execution.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-451 (User Interface (UI) Misrepresentation of Critical Information), CWE-351 (Insufficient Type Distinction)

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


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

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

## Is CVE-2025-31951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31951 is a high-severity command injection vulnerability in HCL BigFix RunBookAI, published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31951 in the wild and no public exploit code.

Affected product: HCL BigFix RunBookAI. 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-31951/ (Markdown: https://insights.sbomify.com/CVE-2025-31951/index.md)
```

## Sources

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

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