CVE-2026-62680

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.22.0, Orval resolves remote and local external $ref values without an allowlist or confinement to the input directory. Processing an attacker-controlled OpenAPI description can cause requests from the developer or CI host to attacker-selected or internal HTTP services, read absolute or out-of-tree local files, and inline untrusted remote schemas into generated clients. The affected code is packages/orval/src/import-specs.ts external reference loading. This issue is fixed in version 8.22.0.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

[SECURITY] Generation-time SSRF + remote/local file inclusion via unrestricted $ref (separate from the comment-injection CVEs) · Advisory · orval-labs/orval · GitHub

https://github.com/orval-labs/orval/security/advisories/GHSA-cxq5-97v7-87j8
github_release Patch Available

Release v8.22.0

Patch available: orval-labs/orval v8.22.0

https://github.com/orval-labs/orval/releases/tag/v8.22.0
github_pr Patch Available

fix(core): gate external $ref resolution behind explicit allow-list

Patch available: orval-labs/orval v8.22.0 (PR #3723 merged 2026-07-14)

https://github.com/orval-labs/orval/pull/3723
github_commit Patch Available

commit 23786c056f4e (orval-labs/orval)

Patch available: orval-labs/orval v8.22.0 (contains commit 23786c056f4e)

https://github.com/orval-labs/orval/commit/23786c056f4eba38c02bf2968677988dbbe4de10

Vendor Advisories for CVE-2026-62680(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
orval—8.22.0—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 01:58 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:26 UTCEG score recompute
  4. 2026-09-16 22:48 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 09:57 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 08:01 UTCEG score recompute
  9. 2026-09-13 17:02 UTCEG score recompute
  10. 2026-09-12 15:29 UTCEG score recompute
  11. 2026-09-12 02:43 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 13:56 UTCEG score recompute
  14. 2026-09-11 09:37 UTCEPSS rescore
  15. 2026-09-10 12:19 UTCEG score recompute
  16. 2026-09-09 02:35 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 18:27 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 16:53 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-06 04:06 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-05 02:30 UTCEG score recompute
  25. 2026-09-04 13:43 UTCEG score recompute
Show 32 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 23:08 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 21:28 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 08:36 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-31 04:53 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 03:21 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 01:48 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 18:44 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 16:24 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 14:47 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 02:01 UTCEG score recompute
  21. 2026-08-24 13:15 UTCEG score recompute
  22. 2026-08-23 11:42 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 10:10 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 08:37 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-20 07:05 UTCEG score recompute
  29. 2026-08-19 18:18 UTCEG score recompute
  30. 2026-08-19 18:13 UTCEG score recompute
  31. 2026-08-19 17:53 UTCEG score recompute
  32. 2026-08-19 17:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62680?
CVE-2026-62680 is a high vulnerability published on August 19, 2026. Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.22.0, Orval resolves remote and local external $ref values without an allowlist or confinement to the input directory. Processing an attacker-controlled OpenAPI description can cause…
When was CVE-2026-62680 disclosed?
CVE-2026-62680 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62680 actively exploited?
CVE-2026-62680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62680?
CVE-2026-62680 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-62680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62680

Explore →

Is Your Infrastructure Affected by CVE-2026-62680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs