orval MCP client is vulnerable to a code injection attack.
CVE-2026-22785 · GHSA-mwr6-3gp8-9jmj · published 2026-01-13
- Severity
- Critical
- CVSS score
- 9.3
- Chance of exploitation (EPSS)
- 0.78%
- Fixed in
- 7.18.0
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Total
- CISA SSVC
The MCP server generation logic relies on string manipulation that incorporates the summary field from the OpenAPI specification without proper validation or escaping. This allows an attacker to "break out" of the string literal and inject arbitrary code. Here is an example OpenAPI with the exploit
Upgrade @orval/mcp to 7.18.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
This is fixed in version 7.18.0 or higher
Do check your generated OpenAPI yaml/json before running through Orval CLI and correct it if it has injection.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @orval/mcp | npm | < 7.18.0 | 7.18.0 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.