CVE-2026-76910: Unleash: Clone-feature lets a user copy a feature from a project they cannot read
Summary The clone-feature endpoint supports copying features across projects, but it does not verify that the caller can access the source project. A user with create permissions in one project can clone a feature from another project they cannot read and then inspect the copied configuration. This vulnerability cannot be confirmed without Enterprise access.
Published Sep 22, 2026
Affected packages
unleash-server
- Ecosystem
- npm
- Affected
- < 8.0.3
- Fixed in
- 8.0.3
- Check
npm ls unleash-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The clone-feature endpoint supports copying features across projects, but it does not verify that the caller can access the source project. A user with _create_ permissions in one project can clone a feature from another project they cannot read and then inspect the copied configuration.
This vulnerability cannot be confirmed without Enterprise access. Report is based on a circumstantial evidence in the open-source repository.
Details
src/lib/features/feature-toggle/feature-toggle-service.ts implements cloneFeatureToggle. This operation needs authorization for both sides: permission to read/copy the source feature and permission to create the destination feature.
The clone path validates permissions against the destination project, but not against the source project that owns featureName. Because feature names are globally unique, a caller can reference a feature outside projects they can access.
PoC
- Create or identify two projects:
P1with a private or restricted feature namedsecret-feature, andP2where the attacker has clone/create permissions. - Authenticate as the attacker.
- Send:
POST /api/admin/projects/P2/features/secret-feature/clone
Content-Type: application/json
{ "name": "secret-feature-copy" }- Open
P2and inspectsecret-feature-copy. Verify if strategy parameters, constraints, variants, and variant payloads from the source feature have been copied.
Impact
Users with permissions on one project can disclose feature configuration from another project if they know or guess the source feature name. Feature names could be available in more public applications that have a common SDK access to multiple projects.
Credited to Tymek.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-76909
Unleash: CR-approval email renders user-controlled raw HTML
low2.1Sep 22, 2026CVE-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
medium4.3Sep 22, 2026CVE-2026-77426
Unleash: Missing await on permission check + cross-project IDOR in admin API
high7.1Sep 22, 2026CVE-2026-63004
Unleash: Addon webhook URL is dialed server-side with no internal-address filtering, enabling SSRF to internal services / cloud metadata and exfiltration of configured request headers
medium5.5Aug 21, 2026CVE-2026-63462
Unleash: Unauthenticated single-request DoS via OpenAPI validation error formatter
high7.5Aug 21, 2026CVE-2026-63466
Unleash: Global Mustache.escape override disables HTML escaping process-wide, enabling Slack/Teams link-injection via unrestricted username
medium4.1Aug 21, 2026
