CVE-2026-76910

Received Received - Intake

Stored Feature Cloning in Unleash Allows Unauthorized Access

Publication date: 2026-09-22

Last updated on: 2026-09-22

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-22

Last Modified

2026-09-22

Generated

2026-09-23

AI Q&A

2026-09-23

EPSS Evaluated

N/A

NVD

CVE-2026-76910

Affected Vendors & Products

Vendor	Product	Version / Range
unleash	unleash	8.0.3

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability affects Unleash, an open-source feature management platform. Before version 8.0.3, the cloneFeatureToggle function and a specific API endpoint allowed users to clone feature toggles without verifying if they had access to the source project. Since feature names are globally unique, an attacker with create or clone permissions in one project could exploit this to copy a feature from another project and inspect sensitive details like strategy parameters, constraints, variants, and payloads.

Detection Guidance

This vulnerability involves unauthorized access to feature toggles across projects due to improper authorization checks. To detect it, review Unleash API logs for suspicious clone or POST requests targeting features from unauthorized projects. Check for requests with mismatched project IDs in the source and destination. No specific commands are provided in the context.

Impact Analysis

If you use Unleash versions prior to 8.0.3, an attacker with limited permissions could access and steal sensitive configuration details from other projects. This could lead to unauthorized changes, data exposure, or compromise of feature management settings across projects.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating GDPR (data protection) and HIPAA (health information privacy) by exposing confidential configurations or user data. Compliance may be impacted if unauthorized access results in data breaches or improper data handling.

Mitigation Strategies

Upgrade Unleash to version 8.0.3 or later to address the authorization bypass in feature cloning.

Hi! I’m here to help you understand CVE-2026-76910. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70