CVE-2026-62680Public exploitNetwork attack vector

SSRF and file inclusion via unrestricted $ref

Published Aug 19, 2026 · Updated Aug 19, 2026

Improper external $ref resolution in Orval before 8.22.0 allows attackers to read local files and trigger build-host SSRF via crafted specs. In packages/orval/src/import-specs.ts, the external reference loader fetched remote URLs and read local file paths named in external $ref values without an allowlist or confinement to the input spec directory, then inlined that content into generated clients. Exploitation requires a developer workstation or CI job to run Orval on an attacker-controlled or attacker-influenced OpenAPI document, and the published advisory bounds the impact to network requests, file reads, and untrusted schema inclusion rather than code execution.

CVSS severity7.1
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper external $ref resolution in Orval before 8.22.0 allows attackers to read local files and trigger build-host SSRF via crafted specs. In packages/orval/src/import-specs.ts, the external reference loader fetched remote URLs and read local file paths named in external $ref values without an allowlist or confinement to the input spec directory, then inlined that content into generated clients. Exploitation requires a developer workstation or CI job to run Orval on an attacker-controlled or attacker-influenced OpenAPI document, and the published advisory bounds the impact to network requests, file reads, and untrusted schema inclusion rather than code execution.

The record

CVE
CVE-2026-62680
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Orval
Product
Orval
Classifications
CWE-918, CWE-829, CWE-22
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=< 8.22.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Orval · Orvalversion=< 8.22.0

Published CVSS scores

7.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
CWE-829Inclusion of Functionality from Untrusted Control Sphere
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Public exploit references

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