Security readout for executives and security teams
Plain-English summary
Orval before 8.21.0 can turn a malicious query-parameter name in an OpenAPI or Swagger specification into executable JavaScript. The code runs when the generated Zod validation module is imported, potentially compromising developer machines, CI systems, tests, or applications.
Executive priority
Prioritize immediate remediation where external, partner, or otherwise mutable specifications feed developer or CI generation. Successful exploitation can execute code with pipeline or application privileges. Upgrade and rebuild generated artifacts promptly, then review credentials and systems if suspicious specifications were processed.
Technical view
The Zod CLI’s query request-validation generator failed to safely encode a double quote in parameter names. This permits computed-property-key injection into generated zod.object code and subsequent JavaScript execution at module import. The affected implementation is packages/zod/src/index.ts. Orval 8.21.0 fixes the issue.
Likely exposure
Exposure requires Orval earlier than 8.21.0, Zod query request-validation generation, and generation from an attacker-controlled or compromised API specification. Importing the resulting module triggers execution. Environments consuming only trusted specifications may face lower likelihood, but compromised upstream specifications remain a supply-chain risk.
Exploitation context
The supplied CVSS 4.0 score is 9.3. The source bundle does not identify known public exploitation, and the CVE is not listed as KEV. Exploitation evidence is therefore incomplete; treat the vulnerability as highly consequential without claiming active attacks.
Researcher notes
CWE mappings are CWE-116, CWE-94, and CWE-95. The vulnerable boundary is specification text becoming JavaScript source without safe encoding. The source bundle identifies query parameter names, generated Zod request-validation objects, and import-time execution. It provides no evidence that unrelated Orval generators or parameter types are affected.
Mitigation direction
- Upgrade Orval to version 8.21.0 or later.
- Regenerate affected Zod validation modules after upgrading.
- Review and restrict which OpenAPI or Swagger specifications can enter generation workflows.
- Check the vendor advisory for any additional guidance or later corrections.
Validation and detection
- Confirm installed and CI-resolved Orval versions are 8.21.0 or later.
- Identify workflows generating Zod query request-validation schemas.
- Inventory generated validation modules created with vulnerable Orval versions.
- Verify generated artifacts were rebuilt after upgrading.
- Review specification sources and update paths for untrusted or compromised inputs.
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-71865 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-653q-5476-x79gCVE 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.