CVE-2026-25141
Orval code injection
- Published30 Jan 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/orval-labs/orval/blob/02211fc413524be340ba9ace866a2ef68845ca7c/packages/core/src/utils/string.ts#L227
- https://github.com/orval-labs/orval/releases/tag/v7.21.0
- https://github.com/orval-labs/orval/releases/tag/v8.2.0
- https://github.com/orval-labs/orval/security/advisories/GHSA-gch2-phqh-fg9q
- https://github.com/orval-labs/orval/security/advisories/GHSA-h526-wf6g-67jv
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-25141 being actively exploited?
CVE-2026-25141 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.69%.
How severe is CVE-2026-25141?
CVE-2026-25141 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.69% probability of exploitation.
Which products are affected by CVE-2026-25141?
Affected products include Orval.
How do I fix CVE-2026-25141?
Upgrade affected software to a fixed version, for example Orval 7.21.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-25141 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.