Security readout for executives and security teams
Plain-English summary
A malicious OpenAPI or Swagger specification can cause vulnerable Orval versions to generate JavaScript that runs attacker-controlled code when imported. This can compromise developer workstations, CI systems, tests, or applications. The issue affects Orval versions before 8.21.0 and is fixed in 8.21.0.
Executive priority
Treat as an urgent software-supply-chain remediation. Prioritize environments processing third-party or externally mutable specifications, especially privileged CI and developer systems. Upgrade and regenerate affected clients promptly; investigate suspicious specifications or generated artifacts before trusting previously produced code.
Technical view
Orval fails to safely encode double quotes in header parameter names while generating Zod request-validation objects. The resulting computed-property-key injection permits JavaScript evaluation when the generated schema module is imported. This is an import-time code-execution flaw categorized under CWE-116, CWE-94, and CWE-95.
Likely exposure
Exposure requires Orval below 8.21.0, header request-validation generation, and import of the generated Zod module. Risk is greatest where OpenAPI or Swagger specifications are externally supplied, fetched from less-trusted locations, or modified through compromised repositories or dependencies.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as KEV. Exploitation could occur during generation and subsequent module import, potentially crossing from an untrusted API specification into developer, CI, testing, or application execution environments.
Researcher notes
The vulnerable path is header request-validation generation in packages/zod/src/index.ts. Impact occurs when injected generated code is imported, not merely when a specification is parsed. Available evidence names the fixed release and implementation change, but provides no confirmed exploitation telemetry.
Mitigation direction
- Upgrade Orval to version 8.21.0 or later.
- Regenerate affected Zod clients using the corrected Orval version.
- Review externally sourced OpenAPI and Swagger specifications before generation.
- Restrict specification modification and code-generation permissions in repositories and CI.
- Check vendor guidance for any additional cleanup or response recommendations.
Validation and detection
- Confirm installed and locked Orval versions are 8.21.0 or later.
- Inventory pipelines and projects generating Zod clients from API specifications.
- Identify whether generated Zod modules from vulnerable versions remain deployed or cached.
- Inspect header parameter names for embedded double quotes or unexpected syntax.
- Regenerate clients and verify generated property keys are safely encoded.
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-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-94: 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 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-71864 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-6437-gxhq-pqv8CVE 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 Encoding or Escaping of Output
Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code
Improper Control of Generation of Code 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.