GHSA-j3rq-4xjw-xg63 — marblerun
GHSA-j3rq-4xjw-xg63 is a security vulnerability in github.com/edgelesssys/marblerun. A fix is available for github.com/edgelesssys/marblerun — see the affected versions and patch details below.
Go package github.com/edgelesssys/marblerun CLI commands susceptible to MITM attacks
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
Any CLI command issued to a Coordinator after the Manifest has been set, is susceptible to be redirected to another MarbleRun Coordinator instance, which runs the same binary, but potentially a different manifest.
Patches
The issue has been patched in v1.4.0
Workarounds
Directly using the REST API of the Coordinator and manually verifying and pinning the certificate to a set Manifest avoids the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/edgelesssys/marblerun | all versions | 1.4.0go get github.com/edgelesssys/marblerun@v1.4.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.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3rq-4xjw-xg63 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-j3rq-4xjw-xg63 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j3rq-4xjw-xg63. 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-j3rq-4xjw-xg63 in your dependencies?
O3 Security finds GHSA-j3rq-4xjw-xg63 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.