PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72716 orval-labs CVE debrief

A critical vulnerability in Orval, a tool for generating type-safe JavaScript clients from OpenAPI v3 and Swagger v2 specifications, allows for code execution in developer, CI, test, or application environments. The issue arises from the unsafe emission of attacker-controlled JavaScript in a module-level template literal during zod schema generation. This occurs when a ${...} expression or backtick is present in a query parameter default value. The vulnerability is fixed in version 8.21.0.

Vendor
orval-labs
Product
orval
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-09-09
Advisory published
2026-08-19
Advisory updated
2026-09-09

Who should care

Developers, CI/CD teams, and security professionals responsible for maintaining and securing applications that utilize Orval-generated JavaScript clients should assess their exposure and apply the fix.

Why it matters

CVE-2026-72716 is a critical vulnerability in Orval that allows for code execution via unsafe JavaScript emission in zod schema generation. Developers and security teams must assess exposure and apply the fix in version 8.21.0 or later.

  • Code execution is possible in developer, CI, test, or application environments where the generated zod schema module is imported.
  • Immediate attention is required to assess exposure and apply the fix.
  • Verification of query parameter default values and ${...} expressions or backticks is necessary.
  • Remediation priority is high due to the critical CVSS score of 9.3.

Technical summary

The vulnerability in Orval arises from the unsafe emission of attacker-controlled JavaScript in a module-level template literal during zod schema generation. This occurs when a ${...} expression or backtick is present in a query parameter default value, allowing for code execution in environments where the generated zod schema module is imported. The affected code is in packages/zod/src/index.ts function formatDefaultValue. The issue is fixed in version 8.21.0, and developers must assess exposure and apply the fix.

Defensive priority

Immediate attention is required to assess exposure and apply the fix, as code execution is possible in environments where the generated zod schema module is imported.

Recommended defensive actions

  • Assess exposure by checking if the affected code is used in your environment, particularly in packages/zod/src/index.ts.
  • Verify if query parameter default values contain ${...} expressions or backticks.
  • Apply the fix by updating to version 8.21.0 or later.
  • Review and monitor environments where the generated zod schema module is imported.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its critical CVSS score of 9.3 and the affected code in packages/zod/src/index.ts function formatDefaultValue. The fix is available in version 8.21.0.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72716 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-72716

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-72716 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72716

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.