dbcve.org
OrvalApplication

CVE-2026-22785

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 7.18.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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. Prior to 7.18.0, the MCP server generation logic relies on string manipulation that incorporates the summary field from the OpenAPI specification without proper validation or escaping. This allows an attacker to "break out" of the string literal and inject arbitrary code. This vulnerability is fixed in 7.18.0.

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

The MCP server generation logic in orval versions prior to 7.18.0 directly incorporates the summary field from OpenAPI v3 or Swagger v2 specifications into string manipulation without validation or escaping. A malicious summary field can break out of the string literal and inject arbitrary code during code generation.

MitigationUpgrade orval to version 7.18.0 or later, then regenerate all client code to ensure the fixed generation logic is applied.

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.18.0

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 determine the installed version
    Affected if Version is below 7.18.0
  2. Identify OpenAPI/Swagger spec files
    Locate all .yaml or .json files containing OpenAPI v3 or Swagger v2 definitions in your project, particularly those with 'summary' fields in operations or endpoints
    Affected if Spec files contain 'summary' fields that get passed to orval for code generation
  3. Inspect generated output for string anomalies
    Examine generated TypeScript/JavaScript files in your orval output directory, looking for unexpected characters, broken strings, or malformed code near where summary values would be inserted
    Affected if Generated code contains malformed strings, unexpected syntax, or apparent code injection patterns
  4. Check for custom summary content
    Review your OpenAPI/Swagger spec files to see if any 'summary' fields contain special characters such as quotes, backticks, backslashes, or template syntax
    Affected if Summary fields contain special characters that could break out of string literals

You are affected if orval version is below 7.18.0 and you generate code from OpenAPI/Swagger specs that contain summary fields, especially those with special characters.

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.18.0 or later
Fixed in 7.18.0
Vendor patch github.com →
Interim mitigation

Upgrade orval to version 7.18.0 or later, then regenerate all client code to ensure the fixed generation logic is applied.

Recommended fix High confidence

7.18.0

  1. Check the current version of Orval installed in your project by running: npm list orval
  2. Upgrade Orval to version 7.18.0 or later by running: npm install orval@^7.18.0
  3. After upgrading, rebuild your project to ensure the new version works correctly with your existing code
  4. Verify that the MCP server generation now properly handles the summary field from OpenAPI specifications

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

Fix this in Orval Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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