GHSA-w7wm-2425-7p2h is a high-severity (CVSS 7.1) vulnerability in github.com/edgelesssys/marblerun. A fix is available for github.com/edgelesssys/marblerun — see the affected versions and patch details below.
MarbleRun unauthenticated recovery allows Coordinator impersonation
Real-World Exposure
github.com/edgelesssys/marblerunReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
During recovery, a Coordinator only verifies that a given recovery key decrypts the sealed state, not if this key was provided by a party with access to one of the recovery keys defined in the manifest. This allows an attacker to manually craft a sealed state using their own recovery keys, and a manifest that does not match the rest of the state.
If network traffic is redirected from the legitimate coordinator to the attacker's Coordinator, a remote party is susceptible to impersonation if they verify the Coordinator without comparing the root certificate of the Coordinator against a trusted reference.
Under these circumstances, an attacker can trick a remote party into trusting the malicious Coordinator by presenting a manifest that does not match the actual state of the deployment.
This issue does not affect the following:
- secrets and state of the legitimate Coordinator instances
- integrity of workloads
- certificates chaining back to the legitimate Coordinator root certificate
Patches
The issue has been patched in v1.7.0.
Workarounds
Connections that purely authenticate based on a known Coordinator's root certificate, e.g. the one retrieved when using the marblerun manifest set CLI command, are not affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/edgelesssys/marblerun | all versions | 1.7.0go get github.com/edgelesssys/marblerun@v1.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgelesssys/marblerun, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/edgelesssys/marblerun to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w7wm-2425-7p2h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w7wm-2425-7p2h can be triaged on real exposure rather than presence alone.
Tailored to GHSA-w7wm-2425-7p2h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w7wm-2425-7p2h in your dependencies?
O3 Security finds GHSA-w7wm-2425-7p2h across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.