Unleash Security Update Addresses 4 Vulnerabilities
Tech GuruQuick Answer
Four Unleash advisories cover approval-email HTML injection and cross-project access-control failures in cloning, strategy ordering and admin APIs. All list 8.0.3 as a patched release, but their original affected ranges differ. Two Enterprise-related reports explicitly lack runtime confirmation. Inventory the deployed release and enabled workflows, then plan a supported upgrade and test project boundaries without changing production flags.
Confirm Scope And Apply The Supported Fix
What to do now: review Unleash versions, project roles and change-request email use. Select a supported release containing the 8.0.3 fixes, accounting for migration requirements from older major versions. Preserve flag configuration and audit evidence before the change.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | Unleash packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-7hvx-28gp-mf6j / GHSA-8xcj-9hfr-fh9j / GHSA-5ffh-6f9q-5hhr / GHSA-72h8-wp98-7hch |
| CVEs | CVE-2026-76909, CVE-2026-76910, CVE-2026-77425, CVE-2026-77426 |
| Authoritative release date | 2026-07-10, 2026-07-13 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-08-20 UTC (project advisory dates, not database ingestion) |
| Affected versions | GHSA-7hvx-28gp-mf6j and GHSA-8xcj-9hfr-fh9j: primary range <=7.6.4.GHSA-5ffh-6f9q-5hhr: primary range <=8.0.0.GHSA-72h8-wp98-7hch: primary range <=6.6.0.The GitHub database summarized these as unleash-server <8.0.3. Resolve intervening-version applicability with Unleash; a narrower original range is not proof of safety. |
| Fixed version | unleash-server 8.0.3 |
| CVSS base score | 2.1 / 4.3 / 5.3 / 7.1 (official CVSS v3/v4 scores) |
| CVSS severity | Low to High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The email finding concerns unescaped fields in approval messages; the clone finding concerns missing source-project authorization. Both reports say Enterprise behavior was not confirmed. The strategy-ordering issue permits a project member with strategy-update permission to alter another project's ordering, with misleading or missing victim-project audit attribution. The fourth advisory groups missing asynchronous authorization and cross-project object checks in the admin API. These are distinct paths, so a single successful login test does not validate the fixes.
What To Validate Now
- Inventory. Record the server version, enabled change-request emails, project roles and integrations that modify flags, strategies, segments or variants.
- Establish applicability. Use each advisory's scope and the range discrepancy above. Do not treat a Community-only test as proof of Enterprise email or cloning behavior.
- Remediate. Apply unleash-server 8.0.3 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. On disposable projects, test authorized flag operations and rejected cross-project reads/writes with low-privilege accounts. Verify audit attribution and, where available, safely rendered approval-email fields. Do not use live production strategies as test targets.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
