# CVE-2026-96758: orval @orval/core before 8.28.0 Code Injection via Form-Data

> Attackers can inject code into generated API clients via malicious OpenAPI schema property names, leading to code execution with consumer privileges.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-f2xw-gqvf-336w, GHSA-jwhm-6748-j6pq

## What is CVE-2026-96758?

CVE-2026-96758 is a critical code injection vulnerability in orval-labs orval, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

orval @orval/core before 8.28.0 contains a code injection vulnerability in the form-data serializer that fails to escape multipart property names in generated template literals. Attackers can inject ${...} expressions into OpenAPI schema property names that execute as live interpolation when the generated client builds FormData bodies with consumer process privileges.

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

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


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

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

## Is CVE-2026-96758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96758 is a critical code injection vulnerability in orval-labs orval, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96758 exists.

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

## Sources

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

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