Описание
Orval has a code injection via unsanitized x-enum-descriptions in enum generation
Impact
Arbitrary code execution in environments consuming generated clients
This issue is similar in nature to the recently-patched MCP vulnerability (CVE-2026-22785), but affects a different code path in @orval/core that was not addressed by that fix.
The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code into generated clients via the x-enumDescriptions field, which is embedded without proper escaping in getEnumImplementation(). I have confirmed that the injection occurs during const enum generation and results in executable code within the generated schema files.
Patches
Upgrade to Orval 8.0.2
References
An example OpenAPI showing the issue:
Ссылки
- https://github.com/orval-labs/orval/security/advisories/GHSA-h526-wf6g-67jv
- https://nvd.nist.gov/vuln/detail/CVE-2026-23947
- https://github.com/orval-labs/orval/commit/9e5d93533904936678ba93b5d20f6bca176a4e1e
- https://github.com/orval-labs/orval/releases/tag/v7.19.0
- https://github.com/orval-labs/orval/releases/tag/v8.0.2
Пакеты
@orval/core
>= 8.0.0-rc.0, < 8.0.2
8.0.2
@orval/core
< 7.19.0
7.19.0
Связанные уязвимости
Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions prior to 7.19.0 until 8.0.2 are vulnerable to arbitrary code execution in environments consuming generated clients. This issue is similar in nature to CVE-2026-22785, but affects a different code path in @orval/core that was not addressed by CVE-2026-22785's fix. The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code into generated clients via the x-enumDescriptions field, which is embedded without proper escaping in getEnumImplementation(). I have confirmed that the injection occurs during const enum generation and results in executable code within the generated schema files. Orval 7.19.0 and 8.0.2 contain a fix for the issue.