Orval: Import-time RCE via schema property name -> computed-property-key injection in the zod client

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 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 · score source

EPSS

• CVE-2026-71866: 0.65% estimated exploitation activity in the next 30 days; percentile 51.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary orval's zod client emits each schema property name as a double-quoted key in the generated zod.object({...}) WITHOUT escaping the double quote. A " in a property name closes the key and lands in object-literal context, where an injected computed property key [expr] is evaluated when zod.object({...}) runs -- which is at MODULE IMPORT (the export const X = zod.object({...}) executes on load) - import-time RCE. The property name is a pure data field. Verified on orval 8.19.0 / Node. CWE-94 / CWE-95 / CWE-116. Details Sibling: the MSW mock uses a single-quoted key (' breakout, call-time) -- separate report. The TS interface key is a type (DoS only). Distinct from orval's $ref / route-path / server-url / zod-default findings. PoC reproduce.sh (+ makespec.py) attached: a property name a":zod.string(),[require("fs").writeFileSync("<marker","")]:zod.string(),"b - zod.object; evaluating it (= importing the module) writes the marker. Verified on 8.19.0. Impact JavaScript / OS command…

Published by the source

2 Sep 2026, 14:52 UTC

Last modified by the source

2 Sep 2026, 15:00 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6mr6-jvcr-2f25

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-6mr6-jvcr-2f25

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-6mr6-jvcr-2f25

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71866

Advisory: Orval: Import-time RCE via schema property name -> computed-property-key injection in the zod client
IDs: CVE-2026-71866, GHSA-6mr6-jvcr-2f25
Record: https://patchnext.com/advisories/cve-2026-71866 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: orval 8.21.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm orval: affected < 8.21.0; fixed in 8.21.0

## Suggested inspection (read-only)
- `npm ls orval --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on orval.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6mr6-jvcr-2f25 (GitHub-reviewed advisory GHSA-6mr6-jvcr-2f25 lists affected ranges: npm orval >=0 <8.21.0)
- Verified: https://osv.dev/vulnerability/GHSA-6mr6-jvcr-2f25 (OSV record GHSA-6mr6-jvcr-2f25 lists affected ranges: npm orval >=0 <8.21.0 (fixed))

Commands are suggestions: review each one before running it.