NPM · SEPTEMBER 2026 · EARLY WARNING

Orval npm Package Vulnerability: Critical RCE Risk

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.21.0 or < 8.21.0 or < 8.21.0 or < 8.21.0 or < 8.22.0 or < 8.21.0
Patched version
Not yet available
GHSA-2W86-XFRC-G85R

An early warning has been issued for a critical remote code execution vulnerability in the orval npm package. Users of affected versions are advised to take immediate action.

What happened

An early warning has been issued regarding a critical remote code execution vulnerability in the orval npm package. The vulnerability, tracked as GHSA-2w86-xfrc-g85r, arises when orval generates MSW mocks and emits schema property names as single-quoted object keys without proper escaping. This behavior can lead to remote code execution. Affected versions include those below 8.21.0.

The vulnerability has not been reported as exploited in the wild. However, due to its critical severity, it is strongly recommended that users assess their exposure and apply the necessary fixes.

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 orval npm package versions below 8.21.0.

What should I do right now?

Upgrade to orval version 8.21.0 or later, or manually apply the suggested fix if upgrading is not possible.

Has this been exploited in the wild?

There are no reports of this vulnerability being exploited in the wild at this time.

Sources

Join the 0Day waitlist →

← Back to all threats