GHSA-J3RQ-4XJW-XG63

GHSA-J3RQ-4XJW-XG63 is a high-severity security vulnerability in github.com/edgelesssys/marblerun (go), affecting versions < 1.4.0. It is fixed in 1.4.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Go package github.com/edgelesssys/marblerun CLI commands susceptible to MITM attacks

Workarounds

Directly using the REST API of the Coordinator and manually verifying and pinning the certificate to a set Manifest avoids the issue.

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.

Affected versions

github.com/edgelesssys/marblerun (< 1.4.0)

Security releases

github.com/edgelesssys/marblerun → 1.4.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

The issue has been patched in v1.4.0

Frequently Asked Questions

  1. What is GHSA-J3RQ-4XJW-XG63? GHSA-J3RQ-4XJW-XG63 is a high-severity security vulnerability in github.com/edgelesssys/marblerun (go), affecting versions < 1.4.0. It is fixed in 1.4.0.
  2. Which versions of github.com/edgelesssys/marblerun are affected by GHSA-J3RQ-4XJW-XG63? github.com/edgelesssys/marblerun (go) versions < 1.4.0 is affected.
  3. Is there a fix for GHSA-J3RQ-4XJW-XG63? Yes. GHSA-J3RQ-4XJW-XG63 is fixed in 1.4.0. Upgrade to this version or later.
  4. Is GHSA-J3RQ-4XJW-XG63 exploitable, and should I be worried? Whether GHSA-J3RQ-4XJW-XG63 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-J3RQ-4XJW-XG63 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-J3RQ-4XJW-XG63? Upgrade github.com/edgelesssys/marblerun to 1.4.0 or later.

Other vulnerabilities in github.com/edgelesssys/marblerun

Stop the waste.
Protect your environment with Kodem.