cve.bz

CVE-2026-63004 unleash unleash: SSRF

5.5 mediumEPSS 0.4%Fix available

Medium (5.5) in unleash unleash. EPSS 0.4% 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 addon and integration subsystem passes the operator-controlled parameters.url value from src/lib/addons/webhook.ts and the Slack, Microsoft Teams, Datadog, and New Relic integrations to Addon.fetchRetry in src/lib/addons/addon.ts without restricting loopback, link-local, private, or cloud metadata addresses. An authenticated actor with the root CREATE_ADDON or UPDATE_ADDON permission can cause the server to send requests from inside its network boundary, use integration event status as a blind probing oracle, forward Authorization, customHeaders, or DD-API-KEY values to an attacker-observed host, and deliver the feature-event JSON body to internal services. This issue is fixed in versions 7.5.2, 7.6.5, and 8.0.2.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd 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: no · Technical impact: partial, assessed 2026-08-21. 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-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
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-63004 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63004?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63004?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-63004 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-5vf6-jrqr-78fjnpmunleash-server<7.5.27.5.2
GHSA-5vf6-jrqr-78fjnpmunleash-server>=7.6.0 <7.6.57.6.5
GHSA-5vf6-jrqr-78fjnpmunleash-server>=8.0.0 <8.0.28.0.2

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

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

References

Check your stackJSON