Skip to content
Applications

CVE-2026-71871

9.3
Critical
EPSS 0.48%Patch availableAug 20, 2026

Code execution via unencoded template literals in Orval-generated zod schemas.

common questions

Is CVE-2026-71871 being exploited?

Not confirmed. CVE-2026-71871 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.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-71871?

CVE-2026-71871 is rated Critical with a CVSS score of 9.3. 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-71871?

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

What does CVE-2026-71871 affect?

CVE-2026-71871 affects Orval (<8.21.0), Generated zod schema modules, TypeScript/Node.js developer and CI environments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71871?

Upgrade Orval to >=8.21.0 and regenerate artifacts; avoid importing modules from untrusted specs.

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

executive summary
technical analysis
affected
Orval (<8.21.0)Generated zod schema modulesTypeScript/Node.js developer and CI environments
impact

Attacker-controlled JavaScript can execute when importing generated zod schema modules, enabling code execution in developer, CI, test, or app environments.

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