CVE-2026-71865: Orval: Import-time RCE via query parameter name -> computed-property-key injection in the zod cli
Summary
orval's zod client emits each query parameter name as a double-quoted key in the generated zod.object({...}) request-validation schema WITHOUT escaping the double quote. A " in the query parameter name closes the key and lands in object-literal context, where an injected computed property key [expr] is evaluated when zod.object({...}) runs -- at MODULE IMPORT (export const OpQueryParams = zod.object({...}) executes on load) -> import-time RCE. The query parameter name is a pure data field. Verified on orval 8.19.0 / Node.
Details
export const OpQueryParams = zod.object({ "a":zod.string(),[require("fs").writeFileSync("PWNED","")]:zod.string(),"b": ... })
Also affects the hono client (reuses zod generation). orval escapes values in zod arrays but not keys in zod.object. Sibling fields: schema property name, header parameter name (CVE-97) (separate reports). Distinct from orval's $ref / route-path / server-url / zod-default findings.
PoC
reproduce.sh (+ makespec.py) attached: a query parameter name that breaks the zod.object key and injects a computed key; evaluating it (= importing the module) writes the marker. Verified on 8.19.0.
Impact
JavaScript / OS command execution at import time for anyone who generates an orval zod client from an attacker-controlled spec and imports it.
Suggested fix
Escape the query parameter name for the JS string key (JSON.stringify) in the zod.object key generation; never interpolate a raw name adjacent to [ ] in object-literal position. maintainer-report.txt makespec.py reproduce.sh
Other sources
Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, a double quote in a query parameter name is emitted into the generated request-validation zod.object({...}) schema without safe encoding. This permits attacker-controlled JavaScript to be evaluated when the generated zod schema module is imported, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/zod/src/index.ts and query request-validation generation. This issue is fixed in version 8.21.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/orvalto a version that resolves this vulnerability.Fixed in 8.21.0 - 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?
Users of Orval versions before 8.21.0 are exposed when generating query request-validation schemas with the zod CLI from an OpenAPI v3 or Swagger v2 specification containing a malicious query parameter name. Code execution occurs when the generated zod schema module is imported, affecting developer, CI, test, or application environments that import it.
What does an attacker need to exploit it?
An attacker needs control over, or the ability to influence, an API specification processed by the affected Orval generation path. The specification must include a query parameter name containing a double quote that injects JavaScript into the generated zod.object({...}) schema.
How can I determine whether generated code is affected?
Review generated query request-validation zod schema modules for query parameter names containing double quotes or unexpected JavaScript in computed property keys. The vulnerable generation logic is in packages/zod/src/index.ts and affects query request-validation generation.
What version fixes the issue?
Upgrade Orval to version 8.21.0, which fixes the unsafe encoding of query parameter names in generated request-validation schemas.