# CVE-2026-31254: Code injection in n/a

> Attackers can execute arbitrary Python code by providing a malicious configuration file to the flash-attention training script.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-9hgr-qwgw-x8pp

## What is CVE-2026-31254?

CVE-2026-31254 is a high-severity code injection vulnerability in n/a, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The flash-attention project thru commit e724e2588cbe754beb97cf7c011b5e7e34119e62 (2025-13-04) contains a code injection vulnerability (CWE-94) in its training script. The script registers the Python eval() function as a Hydra configuration resolver under the name eval. This allows configuration files to execute arbitrary Python code via the ${eval:...} syntax. An attacker can exploit this by providing a malicious configuration file, leading to arbitrary code execution when the training script is run with that configuration.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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


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

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

## Is CVE-2026-31254 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31254 is a high-severity code injection vulnerability in n/a, published on 11 May 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-31254 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-31254/ (Markdown: https://insights.sbomify.com/CVE-2026-31254/index.md)
```

## Sources

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

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