Code execution via mock-factory key injection
Published Aug 19, 2026 · Updated Aug 19, 2026
Code injection in MSW mock generation in Orval before 8.21.0 allows attackers to execute code via crafted schema property names. In packages/core/src/getters/keys.ts, the getKey function wraps non-identifier property names in single quotes and emits them into generated object-literal keys without escaping embedded single quotes, letting a malicious name break out and inject a computed property expression that runs when the mock factory is called. Exposure requires generating MSW mocks from an attacker-controlled or attacker-influenced OpenAPI or Swagger specification and then executing the generated factory in tests or an MSW handler, affecting developer, CI, test, or application environments.
Summary
What happened
Code injection in MSW mock generation in Orval before 8.21.0 allows attackers to execute code via crafted schema property names. In packages/core/src/getters/keys.ts, the getKey function wraps non-identifier property names in single quotes and emits them into generated object-literal keys without escaping embedded single quotes, letting a malicious name break out and inject a computed property expression that runs when the mock factory is called. Exposure requires generating MSW mocks from an attacker-controlled or attacker-influenced OpenAPI or Swagger specification and then executing the generated factory in tests or an MSW handler, affecting developer, CI, test, or application environments.
The record
- CVE
- CVE-2026-71867
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Orval
- Product
- Orval
- Classifications
- CWE-95, CWE-89, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.21.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-2w86-xfrc-g85r reproduce.sh PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo