CVE-2026-77425

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 23, 2026

Advisory Details (3)

Auto-updated Sep 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

v8.0.3

Patch available: Unleash/unleash v8.0.3

https://github.com/Unleash/unleash/releases/tag/v8.0.3
github_commit Patch Available

commit 43e8db37b846 (Unleash/unleash)

Patch available: Unleash/unleash v8.0.3 (contains commit 43e8db37b846)

https://github.com/Unleash/unleash/commit/43e8db37b846921c8a94db58b44935ecbd15d9d1
github Patch Available🟡 PoC Available

A project member can reorder activation strategies belonging to any other project / environment (cross-project integrity write), bypassing project RBAC and the audit log · Advisory · Unleash/unleash · GitHub

https://github.com/Unleash/unleash/security/advisories/GHSA-5ffh-6f9q-5hhr

Vendor Advisories for CVE-2026-77425(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
unleash-server—8.0.3—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-23 18:25 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-23 14:37 UTCEG score recompute
  4. 2026-09-23 13:26 UTCEG score recompute
  5. 2026-09-22 21:33 UTCEG score recompute
  6. 2026-09-22 20:33 UTCEG score recompute
  7. 2026-09-22 20:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77425?
CVE-2026-77425 is a medium vulnerability published on September 22, 2026. 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…
When was CVE-2026-77425 disclosed?
CVE-2026-77425 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77425 actively exploited?
CVE-2026-77425 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.2% of all scored CVEs.
What is the CVSS score of CVE-2026-77425?
CVE-2026-77425 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-77425?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77425, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77425

Explore →

Is Your Infrastructure Affected by CVE-2026-77425?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs