← Back to results
Vulnerability record · public intelligence
CVE-2026-72717
CRITICAL

Orval: Import-time RCE via schema default -> zod module-level template literal

Published Aug 19, 2026 · Updated Oct 23, 2026 · Also known as GHSA-w727-8j6c-2rj4

Severity · CVSSCRITICAL · Not scored
Known exploitationNot listed
EPSS / likelihood0.65%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Orval: Import-time RCE via schema default -> zod module-level template literal

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Orval's zod schema generation emits a schema's default value as a module-level template literal (export const …Default = <default>;) without escaping ${ or the backtick. A default of the form v${<code>}w injects a live JavaScript expression that is evaluated when the generated zod schema module is imported, executing attacker-controlled code at import — no request or function call needed. Verified on Orval 8.19.0; survives default OpenAPI validation.

Potential impact

Code execution at import in any application that imports a zod schema module generated from an attacker-controlled or attacker-influenced OpenAPI description.

Technical context

${...} permits an arbitrary JS expression. Orval escapes its other value sinks (enum, mock, regex, object-default values) with \' inside single-quoted strings; the string default is the one value emitted as a backtick template literal, so ${...}/backtick are interpreted, not escaped. Distinct from the URL-template-literal cases (different field and sink) and from the published Orval CVEs (summary/MCP, x-enumDescriptions, const/mock).

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
Not available
Aliases
GHSA-w727-8j6c-2rj4

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Patch commit ↗
  4. Source repository ↗

Record history

Published Aug 19, 2026 · Last refreshed Oct 23, 2026