CVE-2026-63462

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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.5EG
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.5Exploit: Elevated riskExposed: 0

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

Unleash is an open-source feature management platform. Prior to 7.5.2, 7.6.5, and 8.0.2, the shared OpenAPI validation error path in src/lib/error/bad-data-error.ts passes a raw request value from lodash.get to JSON.stringify in genericErrorMessage and fromOpenApiValidationErrors without guarding stack exhaustion. An unauthenticated attacker can send a roughly 10 KB JSON value nested thousands of levels deep to POST /edge/validate, POST /edge/issue-token, or another OpenAPI-validated endpoint, causing RangeError: Maximum call stack size exceeded in openAPIValidationMiddleware and terminating the Node process because no uncaughtException handler recovers it. Replaying the request can sustain a complete service outage. This issue is fixed in versions 7.5.2, 7.6.5, and 8.0.2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

August 21, 2026

Last Modified

September 9, 2026

Advisory Details (7)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v8.0.2

Patch available: Unleash/unleash v8.0.2

https://github.com/Unleash/unleash/releases/tag/v8.0.2
github_release Patch Available

v7.6.5

Patch available: Unleash/unleash v7.6.5

https://github.com/Unleash/unleash/releases/tag/v7.6.5
github_release Patch Available

v7.5.2

Patch available: Unleash/unleash v7.5.2

https://github.com/Unleash/unleash/releases/tag/v7.5.2
github_commit Patch Available

commit d862562a5ab8 (Unleash/unleash)

Patch available: Unleash/unleash v7.5.2 (contains commit d862562a5ab8)

https://github.com/Unleash/unleash/commit/d862562a5ab8f2d1e40f6519c64cf0b4fdaf806d
github_commit Patch Available

commit d45f99df924c (Unleash/unleash)

Patch available: Unleash/unleash v7.6.5 (contains commit d45f99df924c)

https://github.com/Unleash/unleash/commit/d45f99df924c0d24747b3e45e46fcda7dcd3c1c1
github_commit Patch Available

commit b0e4da63249a (Unleash/unleash)

Patch available: Unleash/unleash v8.0.2 (contains commit b0e4da63249a)

https://github.com/Unleash/unleash/commit/b0e4da63249a9403bc209e0581db223326cb8dcf
github Patch Available

Unauthenticated single-request DoS via OpenAPI validation error formatter · Advisory · Unleash/unleash · GitHub

https://github.com/Unleash/unleash/security/advisories/GHSA-r5pq-6chh-j3xp

Vendor Advisories for CVE-2026-63462(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
unleash-server—8.0.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-63462?
CVE-2026-63462 is a high vulnerability published on August 21, 2026. Unleash is an open-source feature management platform. Prior to 7.5.2, 7.6.5, and 8.0.2, the shared OpenAPI validation error path in src/lib/error/bad-data-error.ts passes a raw request value from lodash.get to JSON.stringify in genericErrorMessage and fromOpenApiValidationErrors without guarding…
When was CVE-2026-63462 disclosed?
CVE-2026-63462 was first published in the National Vulnerability Database on August 21, 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-63462 actively exploited?
CVE-2026-63462 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 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63462?
CVE-2026-63462 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-63462?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63462, 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-63462

Explore →

Is Your Infrastructure Affected by CVE-2026-63462?

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

Start Free Scan →Browse All CVEs