Security readout for executives and security teams
Plain-English summary
A malicious or compromised API specification can make Orval generate JavaScript that runs when the generated Zod client is imported. This could compromise developer workstations, CI systems, test environments, or applications, exposing code, credentials, and build artifacts.
Executive priority
Prioritize immediate remediation wherever Orval processes external or changeable specifications in credentialed developer or CI environments. Upgrade and regenerate affected clients before normal pipeline execution. Systems using only trusted, immutable specifications remain exposed to specification compromise and should still be updated promptly.
Technical view
Orval fails to safely encode a double quote within an OpenAPI schema property name when generating zod.object keys. An attacker controlling the specification can inject JavaScript into the generated module. Importing that module triggers code execution. The bundle identifies 8.21.0 as the fixed release.
Likely exposure
Exposure requires Orval Zod client generation from an attacker-controlled or compromised OpenAPI or Swagger specification, followed by importing the generated module. Internet-facing schema sources, third-party specifications, automated generation pipelines, and committed generated clients increase risk. Other Orval generators are not established as affected by the supplied evidence.
Exploitation context
The CVSS 4.0 score is 9.3 because exploitation can lead to complete confidentiality, integrity, and availability impact in the executing environment. The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle.
Researcher notes
The bundle describes the vulnerable range as 8.19.0 through versions before 8.21.0, while its structured affected field says all versions below 8.21.0. Confirm the precise lower boundary against the vendor advisory. CWE-95 directly matches code injection; the supplied CWE-89 classification appears less specific.
Mitigation direction
- Upgrade Orval to version 8.21.0 or later.
- Regenerate Zod clients only from trusted, reviewed specifications.
- Review previously generated modules before importing or deploying them.
- Treat suspicious generation activity as a potential compromise and rotate exposed credentials.
Validation and detection
- Identify projects and CI workflows using Orval Zod generation.
- Confirm the installed and lockfile-resolved Orval version is 8.21.0 or later.
- Trace the provenance and integrity of every specification used for generation.
- Inspect generated Zod modules for unexpected executable expressions in object keys.
- Review affected environments for unusual processes, network activity, or credential use.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-71866 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: 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 and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/orval-labs/orval/security/advisories/GHSA-6mr6-jvcr-2f25CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/orval-labs/orval/pull/3692CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/orval-labs/orval/commit/8ef1bfdf3f9bcaf9dabfbe2e42887f1c0e159ab6CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/orval-labs/orval/releases/tag/v8.21.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Directives in Dynamically Evaluated Code
Improper Neutralization of Directives in Dynamically Evaluated Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.