dbcve.org
OrvalApplication

CVE-2026-23947

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

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 prior to 7.19.0 until 8.0.2 are vulnerable to arbitrary code execution in environments consuming generated clients. This issue is similar in nature to CVE-2026-22785, but affects a different code path in @orval/core that was not addressed by CVE-2026-22785's fix. The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code into generated clients via the x-enumDescriptions field, which is embedded without proper escaping in getEnumImplementation(). I have confirmed that the injection occurs during const enum generation and results in executable code within the generated schema files. Orval 7.19.0 and 8.0.2 contain a fix for the issue.

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 through 8.0.2 have a code injection vulnerability in the getEnumImplementation() function. The x-enumDescriptions field from OpenAPI specifications is embedded without sanitization into generated TypeScript const enum code, allowing arbitrary JavaScript/TypeScript code execution in environments consuming the generated clients.

MitigationUpgrade Orval to version 7.19.0 or 8.0.2 or later which includes proper escaping of the x-enumDescriptions field. If immediate upgrading is not feasible, avoid processing untrusted OpenAPI specifications that contain x-enumDescriptions.

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:< 7.19.0>= 8.0.0, < 8.0.2

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. Identify installed Orval version
    Run 'npm list orval' or 'yarn list orval' to see the installed version, or check package.json for the orval dependency version
    Affected if The version is < 7.19.0 or >= 8.0.0 but < 8.0.2
  2. Locate OpenAPI specification files processed by Orval
    Search your project for .yaml or .json files containing the 'x-enumDescriptions' field, which is the attack vector for this vulnerability
    Affected if Any OpenAPI spec being processed by Orval contains an x-enumDescriptions field with unsanitized content
  3. Inspect generated TypeScript enum code
    Examine the generated TypeScript output files (look for .ts files with const enum definitions) produced by Orval, specifically looking for enum implementations that may contain raw content from x-enumDescriptions
    Affected if The generated enum code contains unescaped or unescaped content from the x-enumDescriptions field that could represent injected code

A defender is affected if they are using Orval version 7.19.0 through 8.0.2 and processing OpenAPI specifications that contain the x-enumDescriptions field, resulting in generated code that embeds that field's content without sanitization.

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.19.0 / 8.0.2 or later
Fixed in 7.19.08.0.2
Interim mitigation

Upgrade Orval to version 7.19.0 or 8.0.2 or later which includes proper escaping of the x-enumDescriptions field. If immediate upgrading is not feasible, avoid processing untrusted OpenAPI specifications that contain x-enumDescriptions.

Recommended fix High confidence

Orval 7.19.0 (7.x line) or 8.0.2 (8.x line)

  1. Identify the current Orval version in use by checking package.json or running 'npm list @orval/core'
  2. Upgrade to version 7.19.0 or higher for the 7.x release line, OR upgrade to version 8.0.2 or higher for the 8.x release line
  3. Run 'npm install @orval/[email protected]' or 'npm install @orval/[email protected]' (or appropriate version)
  4. Regenerate client code to ensure the fix is applied
  5. Verify the generated code no longer contains unsanitized content from x-enumDescriptions fields

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

Fix this in Orval Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23947 — 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-23947 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