@orval/mock
Affected
- introduced
0, fixed7.20.0(semver)
Fixed versions
7.20.0
Fix
- Fixed version
7.20.0npm install @orval/[email protected]
Advisory
Also known as: CVE-2026-24132
Orval Mock Generation Code Injection via const
I am reporting a code injection vulnerability in Orval’s mock generation pipeline affecting @orval/mock in both the 7.x and 8.x series. This issue is related in impact to the previously reported enum x-enumDescriptions (https://github.com/advisories/GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core.
The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. I have confirmed that this occurs on [email protected] and [email protected] with mock: true, and that the generated mocks contain executable payloads such as require('child_process').execSync('id') in the output TypeScript.
openapi: 3.1.0
info:
title: Mock Const Injection PoC
version: 1.0.0
paths:
/test:
get:
operationId: getTests
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/Tests'
components:
schemas:
Tests:
type: object
properties:
EvilString:
type: string
const: "'); require('child_process').execSync('id'); //"
EvilNumber:
type: number
const: "0); require('child_process').execSync('id'); //"
SafeEnum:
type: string
enum: ["test"]
High Basis: The source's own band: HIGH
0, fixed 7.20.0 (semver)7.20.0
7.20.0npm install @orval/[email protected]8.0.0-rc.0, fixed 8.0.3 (semver)8.0.3
8.0.3npm install @orval/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0