Skip to content

← Actionable
High, CVSS 7.7amended

Orval Mock Generation Code Injection via const

CVE-2026-24132GHSA-f456-rf33-4626

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@orval/mock 8.0.3, 7.20.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @orval/mock

    Affected
    < 7.20.0>= 8.0.0-rc.0, < 8.0.3
    Fixed in
    7.20.0, 8.0.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-24132: 0.74% estimated exploitation activity in the next 30 days; percentile 54.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 orval@7.19.0 and orval@8.0.2 with mock: true, and that the generated mocks contain executable payloads such as…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-f456-rf33-4626

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-f456-rf33-4626

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24132

Advisory: Orval Mock Generation Code Injection via const
IDs: CVE-2026-24132, GHSA-f456-rf33-4626
Record: https://patchnext.com/advisories/cve-2026-24132 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @orval/mock 8.0.3, 7.20.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @orval/mock: affected < 7.20.0; >= 8.0.0-rc.0, < 8.0.3; fixed in 7.20.0, 8.0.3

## Suggested inspection (read-only)
- `npm ls @orval/mock --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @orval/mock.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f456-rf33-4626 (OSV record GHSA-f456-rf33-4626 lists affected ranges: npm @orval/mock >=0 =8.0.0-rc.0 <8.0.3 (fixed))
- Verified: https://github.com/advisories/GHSA-f456-rf33-4626 (GitHub-reviewed advisory GHSA-f456-rf33-4626 lists affected ranges: npm @orval/mock >=0 =8.0.0-rc.0 <8.0.3)

Commands are suggestions: review each one before running it.

Loading voting…