Orval: Generation-time SSRF + remote/local file inclusion via unrestricted $ref

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-62680: 0.40% estimated exploitation activity in the next 30 days; percentile 34.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Orval resolves OpenAPI $refs by fetching remote http(s) URLs and reading local files (including absolute / out-of-tree paths), inlining the referenced schema into the generated client. Running orval on a spec whose $ref points at an attacker/internal URL or an arbitrary local file yields SSRF, remote file inclusion, and local file inclusion. Verified on 8.19.0. This is a different class from Orval's published output-injection CVEs (CVE-2026-22785/23947/24132/25141), none of which covers the $ref resolver. Details - $ref: http://attacker/internal-evil.json#/... → build host fetches (SSRF) and inlines the remote schema (RFI); confirmed property REMOTEORVALPROP in the generated client. - $ref: /abs/path.json#/... or ../../secret.json#/... → out-of-tree local file read + inlined (LFI). No RCE: on 8.19.0 the description JSDoc is escaped (/-\/, the published fix), so $ref content cannot break out into code. The chain stops at SSRF + RFI + LFI. Fix: don't resolve remote $refs by…

Published by the source

2 Sep 2026, 14:54 UTC

Last modified by the source

2 Sep 2026, 14:54 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cxq5-97v7-87j8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62680

Advisory: Orval: Generation-time SSRF + remote/local file inclusion via unrestricted $ref
IDs: CVE-2026-62680, GHSA-cxq5-97v7-87j8
Record: https://patchnext.com/advisories/cve-2026-62680 (revision 1, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: orval 8.22.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm orval: affected < 8.22.0; fixed in 8.22.0

## Suggested inspection (read-only)
- `npm ls orval --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on orval.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cxq5-97v7-87j8 (GitHub-reviewed advisory GHSA-cxq5-97v7-87j8 lists affected ranges: npm orval >=0 <8.22.0)

Commands are suggestions: review each one before running it.