CVE-2026-77425Unleash: A project member can reorder activation strategies belonging to any other project / environment (cross-project integrity write), bypassing project RBAC and the audit log

Official description

Unleash is an open-source feature management platform. Prior to 8.0.3, POST /api/admin/projects/:projectId/features/:featureName/environments/:environment/strategies/set-sort-order passes attacker-controlled strategy IDs to unprotectedUpdateStrategiesSortOrder and updateSortOrder without verifying that the IDs belong to the project, feature, and environment authorized by the URL. In a multi-project Pro or Enterprise deployment, an authenticated user with UPDATE_FEATURE_STRATEGY in one project who knows another project's strategy IDs can reorder those strategies, changing feature evaluation precedence while the operation is attributed to the attacker's URL context rather than the affected project. The single-project OSS edition lacks the cross-project dimension, although the missing context binding still permits unauthorized reordering across features or environments in the default project. The endpoint changes only sort_order and does not modify strategy parameters, constraints, or segments. This issue is fixed in version 8.0.3.

Affected packages & fixed versions

Affected products (as reported)

References

• https://github.com/Unleash/unleash/security/advisories/GHSA-5ffh-6f9q-5hhr x_refsource_CONFIRM
• https://github.com/Unleash/unleash/commit/43e8db37b846921c8a94db58b44935ecbd15d9d1 x_refsource_MISC
• https://github.com/Unleash/unleash/releases/tag/v8.0.3 x_refsource_MISC