Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-76910

Vulnerability in unleash-server (CVE-2026-76910)

Summary

Vulnerability in unleash-server (CVE-2026-76910). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/admin/projects/P2/features/secret-feature/clone. Mitigation: upgrade to 8.0.3 or later.

Original description

The description as published by the source.

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

  1. Create or identify two projects: P1 with a private or restricted feature named secret-feature, and P2 where the attacker has clone/create permissions.
  2. Authenticate as the attacker.
  3. Send:
POST /api/admin/projects/P2/features/secret-feature/clone
Content-Type: application/json

{ "name": "secret-feature-copy" }
  1. Open P2 and inspect secret-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…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-76910 has been found in unleash-server.
Attackers can target a specific entry point like POST /api/admin/projects/P2/features/secret-feature/clone over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade unleash-server to 8.0.3 or later.
If unsure, ask your IT team or search "unleash-server CVE-2026-76910" on the vendor's site.

CVE-2026-76910 (unleash-server) — CWE-639
Attack surface: POST /api/admin/projects/P2/features/secret-feature/clone / cloneFeatureToggle / featureName
Patched: 8.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in unleash-server. Attackers reach the vulnerable code path via POST /api/admin/projects/P2/features/secret-feature/clone.

📍 Affected scope

Check the vendor advisory for the affected versions of unleash-server. Attack surface: POST /api/admin/projects/P2/features/secret-feature/clone / cloneFeatureToggle / featureName.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.0.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/admin/projects/P2/features/secret-feature/clone requests with malformed payloads or SQL meta-characters. Run grep -r 'unleash-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'unleash-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で unleash-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/admin/projects/P2/features/secret-feature/clone' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/admin/projects/P2/features/secret-feature/clone への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade unleash-server to 8.0.3

    ステージング環境で 8.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/admin/projects/P2/features/secret-feature/clone on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm unleash-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details