dbcve.org
OrvalApplication

CVE-2026-25141

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-30
Fix available
A fix is available. Upgrade to 7.21.0 / 8.2.0 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 starting with 7.19.0 and prior to 7.21.0 and 8.2.0 have an incomplete fix for CVE-2026-23947. While the jsStringEscape function properly handles single quotes ('), double quotes (") and so on, it is still possible to achieve code injection using only a limited set of characters that are currently not escaped. The vulnerability lies in the fact that the application can be forced to execute arbitrary JavaScript using characters such as []()!+. By using a technique known as JSFuck, an attacker can bypass the current sanitization logic and run arbitrary code without needing any alphanumeric characters or quotes. Version 7.21.0 and 8.2.0 contain an updated fix.

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's jsStringEscape function has an incomplete fix for XSS/code injection. While it escapes quotes and common characters, it doesn't escape JSFuck characters ([]()!+), allowing attackers to execute arbitrary JavaScript without alphanumeric characters or quotes by encoding malicious code using only these six characters.

MitigationUpgrade Orval to version 7.21.0 or 8.2.0 or later to obtain the complete fix for this code injection vulnerability.

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, < 7.21.0>= 8.0.0, < 8.2.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 Orval package version
    Run 'npm list orval' or check package.json dependencies to find the installed version of Orval
    Affected if Version is >= 7.19.0 and < 7.21.0, or >= 8.0.0 and < 8.2.0
  2. Locate jsStringEscape usage in codebase
    Search project files for 'jsStringEscape' string occurrences using grep or IDE search
    Affected if The jsStringEscape function is used in your codebase and your Orval version falls within the affected ranges
  3. Inspect jsStringEscape implementation for JSFuck character handling
    Find the jsStringEscape function definition in node_modules/orval/dist or within your generated code, and verify whether it escapes the six JSFuck characters: [, ], (, ), !, and +
    Affected if The function does NOT escape one or more of these characters: []()!+ - meaning your generated output could contain unescaped JSFuck characters that may be used for code injection
  4. Check generated output for unescaped JSFuck characters
    Review generated JavaScript/TypeScript files from Orval and search for raw occurrences of [, ], (, ), !, or + within string contexts that originated from user-controlled data
    Affected if Generated code contains unescaped JSFuck characters in string values that could enable code execution

Your environment is affected if you are using a vulnerable Orval version (7.19.0 to < 7.21.0 or 8.0.0 to < 8.2.0) and your generated code contains the jsStringEscape function with unescaped JSFuck 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.21.0 / 8.2.0 or later
Fixed in 7.21.08.2.0
Interim mitigation

Upgrade Orval to version 7.21.0 or 8.2.0 or later to obtain the complete fix for this code injection vulnerability.

Recommended fix High confidence

Upgrade to Orval 7.21.0 (for 7.x users) or 8.2.0 (for 8.x users)

  1. Identify which Orval version line (7.x or 8.x) is currently in use by checking package.json or package-lock.json
  2. For versions 7.19.0 <= current < 7.21.0: Run 'npm install [email protected]' or 'yarn add [email protected]' to upgrade to the fixed release
  3. For versions 8.0.0 <= current < 8.2.0: Run 'npm install [email protected]' or 'yarn add [email protected]' to upgrade to the fixed release
  4. After upgrading, regenerate type-safe clients from OpenAPI specifications to verify the fix is applied
  5. Verify that generated code no longer contains unsanitized input that could be exploited via JSFuck techniques
Caveat Review the release notes for 7.21.0 and 8.2.0 to check for any breaking changes between your current version and the target version

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

Fix this in Orval Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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