# CVE-2026-77425: 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

> An authenticated user can reorder feature strategies in other projects, bypassing RBAC and audit logs, affecting Unleash deployments.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-5ffh-6f9q-5hhr, MINI-vxjc-8pxf-ww8v

## What is CVE-2026-77425?

CVE-2026-77425 is a medium-severity missing authorization vulnerability in unleash, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-77425?

2 open source packages ship an affected version, including unleash-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `unleash-server` | npm | All versions | 8.0.3 |
| `unleash-server` | npm | All versions | 8.0.3 |

## How do I fix CVE-2026-77425?

Upgrade unleash-server to 8.0.3 or later.

## Is CVE-2026-77425 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77425 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77425 and fix it if it is affected.

What it is: CVE-2026-77425 is a medium-severity missing authorization vulnerability in unleash, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77425 exists.

Affected packages and fixed versions:
- unleash-server (npm): affected all versions; fixed in 8.0.3
- unleash-server (npm): affected all versions; fixed in 8.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77425/ (Markdown: https://insights.sbomify.com/CVE-2026-77425/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77425
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77425
- OSV: https://osv.dev/vulnerability/CVE-2026-77425

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77425/
Summaries are generated and may contain mistakes; the official description above is the record.