Skip to content
Applications

CVE-2026-71867

9.3
Critical
EPSS 0.61%Patch availableAug 20, 2026

Code injection via unescaped single quote in Orval-generated MSW mock factories.

common questions

Is CVE-2026-71867 being exploited?

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

How severe is CVE-2026-71867?

CVE-2026-71867 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-71867?

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

What does CVE-2026-71867 affect?

CVE-2026-71867 affects Orval < 8.21.0, TypeScript projects using Orval-generated MSW mocks, MSW handlers invoking generated mocks, CI/test runners executing mocks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71867?

Upgrade Orval to >=8.21.0; sanitize or reject untrusted OpenAPI specs; avoid running untrusted mocks.

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

executive summary
technical analysis
affected
Orval < 8.21.0TypeScript projects using Orval-generated MSW mocksMSW handlers invoking generated mocksCI/test runners executing mocks
impact

Arbitrary JavaScript execution in developer, CI, test, or application environments via crafted OpenAPI schema property names.

action required

Patch when possible

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