EUVD-2026-84867
GHSA-72h8-wp98-7hch
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network admin API, low complexity, any authenticated user (PR:L, not PR:N); cross-project reads give C:L while the missing-await segment/strategy tampering gives I:H; no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
5DescriptionCVE.org
Unleash is an open-source feature management platform. Prior to 8.0.3, the Unleash admin API contains five authorization vulnerabilities. POST /api/admin/segments/strategies assigns the Promise returned by hasPermission without awaiting it, allowing authenticated users to modify segment assignments without UPDATE_FEATURE_STRATEGY permission for the target project and environment. GET /api/admin/projects/:projectId/features/:featureName/environments/:environment/variants does not bind the requested feature to projectId, allowing cross-project variant configuration disclosure. GET .../strategies/:strategyId uses strategyId without validating the project and feature context, allowing cross-project strategy configuration disclosure. getEnvironmentInfo does not validate that the requested feature belongs to the supplied project, allowing cross-project environment information disclosure. PUT /:projectId/tags accepts feature identifiers without verifying that they belong to the URL project, allowing cross-project tag modification. This issue is fixed in version 8.0.3.
Articles & Coverage 1
AnalysisAI
Authenticated users of Unleash (the open-source feature management platform) can bypass project-scoped authorization and reach configuration data and write operations belonging to projects and environments they should not control, due to a cluster of broken-access-control defects fixed in version 8.0.3. The most serious is a missing await on an async permission check in POST /api/admin/segments/strategies, which lets any authenticated account with an admin-API session modify segment assignments on any strategy in any project; four additional cross-project IDOR issues (CWE-639) expose variant configurations, strategy configurations, environment information, and permit tag modification across project boundaries. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires a valid authenticated Unleash account of any privilege level (PR:L) that can reach the admin API over the network; no user interaction and no admin/project-owner role is needed. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine, well-substantiated broken-access-control cluster (CWE-639 IDOR) rather than a high-CVSS-but-low-risk theoretical issue, but its real-world severity is moderate and bounded by the PR:L requirement. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade unleash-server to 8.0.3 or later (the upstream release https://github.com/Unleash/unleash/releases/tag/v8.0.3 carries the fixes described in advisory https://github.com/Unleash/unleash/security/advisories/GHSA-72h8-wp98-7hch and applied in commits 7bb2829fc40791aa478e8ffca149c11b0f9cb05a, ace121c922d2e3eb6f68d95b0b6ab2fc8d824ea1, bea7effd3687425630423f662136d548e100154d, c93a963e95e1b7bf1bca2a7729282a48d0eb2f6a, and dd61d0e10f5977a2e5de78df467c3a17c09fbcef); the change adds the missing `await` on the hasPermission() call in the segments/strategies handler and inserts validateFeatureBelongsToProject checks into getEnvironmentInfo, the variants and strategy read paths, and the tag update path. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every Unleash deployment, record its exact version, and isolate any instance running a release below 8.0.3 by restricting the admin API to trusted management networks or VPN-only reachability; simultaneously identify all accounts with network reach to the admin API, reduce them to the minimum necessary set, and preserve audit logs for review of POST /api/admin/segments/strategies calls and unusual cross-project reads of segment, strategy, variant, environment, and tag data. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today