dbcve.org
OrvalApplication

CVE-2026-24132

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to 7.20.0 / 8.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions 7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow 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. The vulnerability is similar in impact to the previously reported enum x-enumDescriptions (GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core. The issue has been fixed in versions 7.20.0 and 8.0.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Orval versions 7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code via the const keyword on schema properties. These values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, causing attacker-controlled code to be emitted into generated interface definitions and faker/MSW handlers.

MitigationUpgrade to Orval version 7.20.0 or 8.0.3 to receive the patch. If upgrading is not immediately possible, validate and sanitize all OpenAPI specifications from untrusted sources before processing them with Orval.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OrvalApplication
Affected:>= 6.0.0, < 7.20.0>= 8.0.0, < 8.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Orval version
    Run 'npm list orval' or 'orval --version' to see the exact version installed in your project
    Affected if Version is >= 6.0.0 and < 7.20.0, or >= 8.0.0 and < 8.0.3
  2. Verify mock generation is enabled
    Inspect your Orval configuration file (orval.config.ts/js) for the 'mock' output type in your generator settings
    Affected if Mock output is enabled and generating code from OpenAPI specifications
  3. Inspect OpenAPI specs for const keyword usage
    Search your OpenAPI specification files for schema properties using the 'const' keyword in their JSON/YAML definitions
    Affected if Any OpenAPI spec being processed contains 'const' values on schema properties from untrusted sources
  4. Review generated mock files for injected code
    Examine generated output in packages/mock/src/faker/getters/scalar.ts or the generated TypeScript files for unexpected code patterns, especially around scalar type handling
    Affected if Generated mock files contain unexpected JavaScript/TypeScript code that was not in your original specification

You are affected if your Orval version falls within the vulnerable ranges AND you generate mocks from OpenAPI specifications that may contain attacker-controlled 'const' values in schema properties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.20.0 / 8.0.3 or later
Fixed in 7.20.08.0.3
Vendor patch github.com →
Interim mitigation

Upgrade to Orval version 7.20.0 or 8.0.3 to receive the patch. If upgrading is not immediately possible, validate and sanitize all OpenAPI specifications from untrusted sources before processing them with Orval.

Recommended fix High confidence

Upgrade to Orval 7.20.0 (if on v7.x line) or 8.0.3 (if on v8.x line)

  1. 1. Identify the current Orval version in your project by checking package.json or running `npm list orval`
  2. 2. Determine which major version line you are using (v7.x or v8.x)
  3. 3. If using version 7.x (>= 6.0.0, < 7.20.0): run `npm install [email protected]` or `yarn add [email protected]`
  4. 4. If using version 8.x (>= 8.0.0, < 8.0.3): run `npm install [email protected]` or `yarn add [email protected]`
  5. 5. Verify the upgrade was successful by running `npm list orval`
  6. 6. Regenerate your type-safe clients and mocks to ensure the patch is applied to newly generated code
  7. 7. Review generated mock files to confirm no malicious const values are present from any previously processed untrusted OpenAPI specs
Caveat Patch releases typically contain no breaking changes; consult the changelog for any minor changes between your version and 7.20.0/8.0.3

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Orval Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,792.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24132 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data