Skip to content
Applications

CVE-2026-72717

CRITICAL
Critical
EPSS 0.66%Patch availableAug 20, 2026

Orval <8.21.0 allows arbitrary JS execution via unescaped schema defaults on import.

common questions

Is CVE-2026-72717 being exploited?

Not confirmed. CVE-2026-72717 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.

How severe is CVE-2026-72717?

CVE-2026-72717 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72717?

Yes. A fix has been recorded for CVE-2026-72717. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72717 affect?

CVE-2026-72717 affects Orval < 8.21.0, Generated zod schema modules, Developer/CI/test environments, Apps importing generated clients. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72717?

Upgrade Orval to >=8.21.0, rebuild generated modules, and validate/spec sanitize inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Orval < 8.21.0Generated zod schema modulesDeveloper/CI/test environmentsApps importing generated clients
impact

Arbitrary JavaScript execution on module import (RCE) in developer, CI, test, or app environments via crafted OpenAPI defaults.

action required

Immediate action required

affected versions
orval-labs orval
  • affected< 8.21.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free