CVE-2026-62681: Orval: RCE via OpenAPI path -> unescaped request-URL template literal (backtick breakout)
Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, an unescaped backtick in an OpenAPI path is emitted into request URL template literals generated for axios, fetch, react-query, and SWR clients without safe encoding. This permits attacker-controlled JavaScript to be evaluated when a generated request, URL-builder, or query-key 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 and route generation consumers. This issue is fixed in version 8.21.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Orvalto a version that resolves this vulnerability.Fixed in 8.21.0
Event History
Frequently Asked Questions
Who is exposed to this issue?
Teams using Orval before 8.21.0 to generate axios, fetch, react-query, or SWR clients from OpenAPI v3 or Swagger v2 specifications are exposed when a processed specification contains an attacker-controlled backtick in a path.
What must happen for code execution to occur?
An attacker must cause a malicious OpenAPI path to be included in generated code, and a generated request, URL-builder, or query-key function containing that path must be called. The injected JavaScript then executes in the developer, CI, test, or application environment where that generated code runs.
Which versions contain the fix?
The issue is fixed in Orval 8.21.0. Versions prior to 8.21.0 are affected.
How can I determine whether generated code is affected?
Review the OpenAPI or Swagger specifications used for generation for path values containing backticks, then inspect generated request URL template literals and related URL-builder or query-key functions. A backtick emitted unescaped into those generated template literals indicates exposure.