cve.bz

CVE-2026-63462 unleash unleash: Uncontrolled Recursion

7.5 highEPSS 0.7%Fix available

High (7.5) in unleash unleash. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in unleash-server 7.5.2, 7.6.5, 8.0.2.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • unleash-server (npm): fixed in 7.5.2, 7.6.5, 8.0.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-63462 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63462?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63462?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63462 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
unleash< 7.5.2
unleash>= 7.6.0, < 7.6.5
unleash>= 8.0.0, < 8.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r5pq-6chh-j3xpnpmunleash-server<7.5.27.5.2
GHSA-r5pq-6chh-j3xpnpmunleash-server>=7.6.0 <7.6.57.6.5
GHSA-r5pq-6chh-j3xpnpmunleash-server>=8.0.0 <8.0.28.0.2

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON