Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25141 is a critical-severity Code Injection (CWE-94) vulnerability in Orval Orval. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25141 is a code injection vulnerability (CWE-94) in Orval, a tool that generates type-safe JavaScript/TypeScript clients from OpenAPI v3 or Swagger v2 specifications. It stems from an incomplete fix for CVE-2026-23947 in Orval versions starting from 7.19.0 and prior to 7.21.0, as well as versions prior to 8.2.0. The issue resides in the jsStringEscape function within Orval's core utilities, which adequately escapes quotes but fails to handle certain characters like [], (), !, and +. This allows attackers to bypass sanitization using JSFuck techniques to craft payloads that execute arbitrary JavaScript without alphanumeric characters or quotes. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).
Any remote attacker with network access can exploit this vulnerability without authentication, privileges, or user interaction (AV:N/AC:L/PR:N/UI:N). By supplying a malicious OpenAPI or Swagger specification to a vulnerable Orval instance, an attacker can force the execution of arbitrary JavaScript code during client generation. Successful exploitation grants high confidentiality, integrity, and availability impacts (C:H/I:H/A:H), potentially leading to full compromise of the developer's machine running Orval, such as data theft, malware deployment, or further lateral movement.
Orval's security advisories (GHSA-gch2-phqh-fg9q and GHSA-h526-wf6g-67jv) and release notes for versions 7.21.0 and 8.2.0 detail an updated fix to the jsStringEscape function that addresses the bypass. Security practitioners should immediately upgrade affected Orval installations to version 7.21.0 or later for the 7.x branch, or 8.2.0 or later for the 8.x branch, and review any generated clients from untrusted specifications. The specific code changes are visible in the Orval repository at packages/core/src/utils/string.ts.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5007
Vulnerability Data
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 ('),…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation finds code paths that accept and execute externally influenced strings.
Input validation directly stops untrusted data from being used to construct executable code without neutralization.
Least privilege limits the damage an injected code fragment can perform once executed.
Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.