# CVE-2026-62682: Orval: RCE via servers[].url -> unescaped request-URL template literal (with getBaseUrlFromSpecification)

> Attackers can execute arbitrary JavaScript in developer or CI environments by injecting backticks into OpenAPI server URLs when specific configuration options are enabled.

- **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:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-88f2-fpv8-89q2, ROOT-APP-NPM-CVE-2026-62682

## What is CVE-2026-62682?

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

### Official description

Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, an unescaped backtick in servers[0].url is emitted into request URL template literals generated when output.baseUrl.getBaseUrlFromSpecification is enabled without safe encoding. This permits attacker-controlled JavaScript to be evaluated when a generated request or URL-builder function is called, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/core/src/getters/route.ts function getFullRoute. This issue is fixed in version 8.21.0.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine), CWE-116 (Improper Encoding or Escaping of Output)

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

2 open source packages ship an affected version, including orval.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `orval` | npm | All versions | 8.21.0 |
| `orval` | npm | All versions | 8.21.0 |

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

Upgrade orval to 8.21.0 or later.

## Is CVE-2026-62682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62682 is a critical code injection vulnerability in orval-labs orval, published on 19 Aug 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-62682 exists.

Affected packages and fixed versions:
- orval (npm): affected all versions; fixed in 8.21.0
- orval (npm): affected all versions; fixed in 8.21.0

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-62682/ (Markdown: https://insights.sbomify.com/CVE-2026-62682/index.md)
```

## Sources

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

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