{"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-76910 exists.","fix":"Upgrade unleash-server to 8.0.3 or later.","what":"CVE-2026-76910 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-76910 and fix it if it is affected.\n\nWhat it is: CVE-2026-76910 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-76910 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-76910/ (Markdown: https://insights.sbomify.com/CVE-2026-76910/index.md)","id":"CVE-2026-76910","markdown":"https://insights.sbomify.com/CVE-2026-76910/index.md","name":"CVE-2026-76910","record":{"aliases":["GHSA-8xcj-9hfr-fh9j","MINI-v9mx-5jv3-52fr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Feature management platform","requires_auth":"low_privilege","summary":"Attackers can clone features from unauthorized projects to inspect sensitive configuration data if they have clone permissions in another project.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Unleash is an open-source feature management platform. Prior to 8.0.3, cloneFeatureToggle and POST /api/admin/projects/:projectId/features/:featureName/clone authorize creation in the destination project but do not verify access to the source project. Because feature names are globally unique, a user with create or clone permission in one project who knows or guesses another project's feature name can copy that feature into the authorized project and inspect its strategy parameters, constraints, variants, and variant payloads. 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: Clone-feature lets a user copy a feature from a project they cannot read","id":"CVE-2026-76910","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":"Heap-based Buffer Overflow in Wireshark","id":"CVE-2026-76917"},"packages":[{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":null,"source":"GHSA-8xcj-9hfr-fh9j"},{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":"pkg:npm/unleash-server","source":"GHSA-8xcj-9hfr-fh9j"}],"prev":{"headline":"Unleash: CR-approval email renders user-controlled raw HTML","id":"CVE-2026-76909"},"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":"Attackers can clone features from unauthorized projects to inspect sensitive configuration data if they have clone permissions in another project.","url":"https://insights.sbomify.com/CVE-2026-76910/"}