Homepage

Authorization Bypass Through User-Controlled Key Affecting unleash-server package, versions <8.0.3-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.48% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-UNLEASHSERVER-20067784
  • published24 Sept 2026
  • disclosed22 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 22 Sep 2026

NewCVE-2026-77426  (opens in a new tab)
CWE-639  (opens in a new tab)
CWE-862  (opens in a new tab)

How to fix?

Upgrade Minimos:latest unleash-server to version 8.0.3-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream unleash-server package and not the unleash-server package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.