Orval: Import-time RCE via query parameter name -> computed-property-key injection in the zod cli

published 2026-08-19 2 mo ago modified 2026-09-18 52 d ago also GHSA-653q-5476-x79g , EUVD-2026-62604

cvss: 9.3; version 4.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 3

npm orval 8.21.0

github.com/orval-labs/orval@8ef1bfd commit
github.com/orval-labs/orval#3692 pull request
github.com/orval-labs/orval/releases/tag/v8.21.0 release

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 2 mo ago (2026-08-21)

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	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
CNA	4.0	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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem	package	affected	fixed in
npm	orval	<8.21.0	8.21.0

Affected products

orval-labs orval

Classification

Weakness

CWE-94 Improper Control of Generation of Code
CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code
CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary