CVE-2026-62681

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.3Exploit: 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.21.0, an unescaped backtick in an OpenAPI path is emitted into request URL template literals generated for axios, fetch, react-query, and SWR clients without safe encoding. This permits attacker-controlled JavaScript to be evaluated when a generated request, URL-builder, or query-key function is called, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/core/src/getters/route.ts and route generation consumers. This issue is fixed in version 8.21.0.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
73(Attend)
EG Risk 73/100SSVC: Attend

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
Severity93% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (4)

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

[SECURITY] RCE via OpenAPI path -> unescaped request-URL template literal (backtick breakout) · Advisory · orval-labs/orval · GitHub

https://github.com/orval-labs/orval/security/advisories/GHSA-fg9p-mrxr-hvq7
github_release Patch Available

Release v8.21.0

Patch available: orval-labs/orval v8.21.0

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

fix: escape spec-controlled strings in generated template literals and object keys

Patch available: orval-labs/orval v8.21.0 (PR #3692 merged 2026-07-12)

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

commit 8ef1bfdf3f9b (orval-labs/orval)

Patch available: orval-labs/orval v8.21.0 (contains commit 8ef1bfdf3f9b)

https://github.com/orval-labs/orval/commit/8ef1bfdf3f9bcaf9dabfbe2e42887f1c0e159ab6

Vendor Advisories for CVE-2026-62681(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.21.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 54× 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-18 23:48 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:30 UTCEG score recompute
  4. 2026-09-16 14:34 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 09:50 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 06:18 UTCEG score recompute
  9. 2026-09-13 19:18 UTCEG score recompute
  10. 2026-09-12 16:59 UTCEG score recompute
  11. 2026-09-11 18:46 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 10:04 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 20:01 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 15:14 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 17:28 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 18:51 UTCEG score recompute
  25. 2026-09-04 05:09 UTCEG score recompute
Show 32 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 16:06 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 17:45 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 08:59 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 21:31 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 04:07 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 01:49 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 15:56 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 18:12 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 15:43 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 17:56 UTCEG score recompute
  21. 2026-08-24 13:36 UTCEG score recompute
  22. 2026-08-23 02:50 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 00:44 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 20:23 UTCEG score recompute
  27. 2026-08-21 19:55 UTCEG score recompute
  28. 2026-08-21 00:45 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-19 18:18 UTCEG score recompute
  31. 2026-08-19 17:43 UTCEG score recompute
  32. 2026-08-19 17:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62681?
CVE-2026-62681 is a critical vulnerability published on August 19, 2026. Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, an unescaped backtick in an OpenAPI path is emitted into request URL template literals generated for axios, fetch, react-query, and SWR clients without safe encoding. This…
When was CVE-2026-62681 disclosed?
CVE-2026-62681 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-62681 actively exploited?
CVE-2026-62681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.8% of all scored CVEs.
What is the CVSS score of CVE-2026-62681?
CVE-2026-62681 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-62681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62681, 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-62681

Explore →

Is Your Infrastructure Affected by CVE-2026-62681?

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

Start Free Scan →Browse All CVEs