NPM · SEPTEMBER 2026 · EARLY WARNING

Orval npm Package Vulnerability: Import-time RCE via Header Parameter

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
orval (npm)
Affected versions
< 8.21.0 or < 8.22.0 or < 8.21.0
Patched version
Not yet available
GHSA-6437-GXHQ-PQV8

An early warning has been issued for a high-severity vulnerability in the Orval npm package. The vulnerability, which allows for import-time remote code execution via header parameter name injection, affects versions less than 8.21.0 or 8.22.0.

What happened

An early warning has been issued regarding a vulnerability in the Orval npm package. This vulnerability allows for import-time remote code execution (RCE) via header parameter name injection. The issue arises when generating a zod client from an attacker-controlled spec and importing it. The vulnerability is reportedly under investigation and has not been exploited in the wild.

The vulnerability affects versions of the Orval npm package that are less than 8.21.0 or 8.22.0. Users of these versions are advised to avoid generating zod clients from untrusted sources until a patch is released. It is recommended to monitor for updates and apply them promptly once they become available.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If orval is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using a version of the Orval npm package that is less than 8.21.0 or 8.22.0.

What should I do right now?

Avoid generating Orval zod clients from untrusted sources and monitor for updates from the primary sources.

Is there an official fix available?

No official fix has been published yet. Monitor the primary sources for updates.

Sources

Join the 0Day waitlist →

← Back to all threats