{"answers":{"affected":"2 open source packages ship an affected version, including unleash-server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77425 exists.","fix":"Upgrade unleash-server to 8.0.3 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-77425 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77425 exists.\n\nAffected packages and fixed versions:\n- unleash-server (npm): affected all versions; fixed in 8.0.3\n- unleash-server (npm): affected all versions; fixed in 8.0.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77425/ (Markdown: https://insights.sbomify.com/CVE-2026-77425/index.md)","id":"CVE-2026-77425","markdown":"https://insights.sbomify.com/CVE-2026-77425/index.md","name":"CVE-2026-77425","record":{"aliases":["GHSA-5ffh-6f9q-5hhr","MINI-vxjc-8pxf-ww8v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Feature management platform","requires_auth":"low_privilege","summary":"An authenticated user can reorder feature strategies in other projects, bypassing RBAC and audit logs, affecting Unleash deployments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"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","id":"CVE-2026-77425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Unleash: Missing await on permission check + cross-project IDOR in admin API","id":"CVE-2026-77426"},"packages":[{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":null,"source":"GHSA-5ffh-6f9q-5hhr"},{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":"pkg:npm/unleash-server","source":"GHSA-5ffh-6f9q-5hhr"}],"prev":{"headline":"JLine: ReDoS in Built-in Less Viewer Search","id":"CVE-2026-77423"},"products":["unleash"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Unleash"]},"summary":"An authenticated user can reorder feature strategies in other projects, bypassing RBAC and audit logs, affecting Unleash deployments.","url":"https://insights.sbomify.com/CVE-2026-77425/"}