CVE-2026-25141 json
Orval has a code injection via unsanitized x-enum-descriptions uing JS comments
published 9mo ago modified 4mo ago also GHSA-gch2-phqh-fg9q , EUVD-2026-5007
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @orval/core 7.21.0, 8.2.0
- orval orval 7.21.0, 8.2.0
Is CVE-2026-25141 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9mo ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | 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 |
| CNA | 4.0 | 9.3 | 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:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @orval/core | >=7.19.0, <7.21.0 >=8.0.0, <8.2.0 |
7.21.0 8.2.0 |
Affected products
- orval-labs orval
Classification
References
-
github.com
/orval-labs/orval/security/advisories/GHSA-gch2-phqh-fg9q
web, vendor-advisory
-
github.com
/orval-labs/orval/security/advisories/GHSA-h526-wf6g-67jv
web, vendor-advisory
-
github.com
/orval-labs/orval/blob/02211fc413524be340ba9ace866a2ef68845ca7c/packages/core/src/utils/string.ts#L227
web, product
-
github.com
/orval-labs/orval/releases/tag/v7.21.0
web, product, release-notes
-
github.com
/orval-labs/orval/releases/tag/v8.2.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-25141
advisory
-
github.com
/orval-labs/orval
package
Sources
- CVE List CVE-2026-25141
- GitHub Advisory GHSA-gch2-phqh-fg9q
- NVD CVE-2026-25141
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.