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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-77425: 0.33% estimated exploitation activity in the next 30 days; percentile 25.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Unleash scopes write permissions per project and per environment: a user with the UPDATEFEATURESTRATEGY permission on project A is supposed to be able to mutate activation strategies only within project A. The endpoint POST /api/admin/projects/:projectId/features/:featureName/environments/:environment/strategies/set-sort-order violates this. The RBAC middleware authorizes the request against the :projectId taken from the URL, but the handler then writes the strategy IDs supplied in the request body directly to the database by primary key, without ever verifying that those strategy IDs actually belong to the URL's project / feature / environment. A low-privilege member of any one project can therefore reorder the activation strategies of features in any other project and environment — including projects they have no role on at all — by putting their own project in the URL (to satisfy RBAC) and the victim project's strategy IDs in the body. The sibling write paths in the same…

Published by the source

22 Sep 2026, 20:36 UTC

Last modified by the source

22 Sep 2026, 21:00 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5ffh-6f9q-5hhr

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-5ffh-6f9q-5hhr

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-5ffh-6f9q-5hhr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-77425

Advisory: Unleash: A project member can reorder activation strategies belonging to any other project / environment (cross-project integrity write), bypassing project RBAC and the audit log
IDs: CVE-2026-77425, GHSA-5ffh-6f9q-5hhr
Record: https://patchnext.com/advisories/cve-2026-77425 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: unleash-server 8.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm unleash-server: affected < 8.0.3; fixed in 8.0.3

## Suggested inspection (read-only)
- `npm ls unleash-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on unleash-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5ffh-6f9q-5hhr (GitHub-reviewed advisory GHSA-5ffh-6f9q-5hhr lists affected ranges: npm unleash-server >=0 <8.0.3)
- Verified: https://osv.dev/vulnerability/GHSA-5ffh-6f9q-5hhr (OSV record GHSA-5ffh-6f9q-5hhr lists affected ranges: npm unleash-server >=0 <8.0.3 (fixed))

Commands are suggestions: review each one before running it.