Summary
Transparent TLS may not be applied to Marbles with certain manifest configurations
Transparent TLS (TTLS) is a MarbleRun feature that wraps plain TCP connections between Marbles in TLS.
In the manifest, a user defines the connections that should be considered.
Workarounds
Make sure that all Marbles that use TTLS have an environment variable defined in their parameters.
References
For a description of TTLS, see https://docs.edgeless.systems/marblerun/features/transparent-TLS
See the updated section on TTLS configuration in the manifest: https://docs.edgeless.systems/marblerun/workflows/define-manifest#tls
Impact
If a Marble is configured for TTLS, but doesn't have an environment variable defined in its parameters, TTLS is not applied.
The traffic will not be encrypted.
MarbleRun deployments that don't use TTLS (which is only available with EGo Marbles) are not affected.
GHSA-X5R5-2QRX-RQJ8 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.1.
Frequently Asked Questions
- What is GHSA-X5R5-2QRX-RQJ8? GHSA-X5R5-2QRX-RQJ8 is a critical-severity security vulnerability in github.com/edgelesssys/marblerun (go), affecting versions < 1.4.1. It is fixed in 1.4.1.
- How severe is GHSA-X5R5-2QRX-RQJ8? GHSA-X5R5-2QRX-RQJ8 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/edgelesssys/marblerun are affected by GHSA-X5R5-2QRX-RQJ8? github.com/edgelesssys/marblerun (go) versions < 1.4.1 is affected.
- Is there a fix for GHSA-X5R5-2QRX-RQJ8? Yes. GHSA-X5R5-2QRX-RQJ8 is fixed in 1.4.1. Upgrade to this version or later.
- Is GHSA-X5R5-2QRX-RQJ8 exploitable, and should I be worried? Whether GHSA-X5R5-2QRX-RQJ8 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
- What actually determines whether GHSA-X5R5-2QRX-RQJ8 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.
- How do I fix GHSA-X5R5-2QRX-RQJ8? Upgrade
github.com/edgelesssys/marblerunto 1.4.1 or later.