Summary
Constallation has pods exposed to peers in VPC
Workarounds
This network policy excludes all world traffic. It mitigates the problem, but will also block all desired external traffic. If vulnerable pods are known, a policy can be crafted to only firewall those instead (see also https://docs.cilium.io/en/stable/security/policy/language/#access-to-from-outside-cluster).
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
name: "from-world-to-role-public"
spec:
endpointSelector:
matchLabels: {}
# role: public
ingressDeny:
- fromEntities:
- world
References
The tracking bug for a Cilium-side fix is https://github.com/cilium/cilium/issues/25626.
Impact
Cilium allows outside actors (world entity) to directly access pods with their internal pod IP, even if they are not exposed explicitly (e.g. via LoadBalancer). A pod that does not authenticate clients and that does not exclude world traffic via network policy may leak sensitive data to an attacker inside the cloud VPC.
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 v2.16.3.
Frequently Asked Questions
- What is GHSA-G8FC-VRCG-8VJG? GHSA-G8FC-VRCG-8VJG is a high-severity security vulnerability in github.com/edgelesssys/constellation/v2 (go), affecting versions < 2.16.3. It is fixed in 2.16.3.
- Which versions of github.com/edgelesssys/constellation/v2 are affected by GHSA-G8FC-VRCG-8VJG? github.com/edgelesssys/constellation/v2 (go) versions < 2.16.3 is affected.
- Is there a fix for GHSA-G8FC-VRCG-8VJG? Yes. GHSA-G8FC-VRCG-8VJG is fixed in 2.16.3. Upgrade to this version or later.
- Is GHSA-G8FC-VRCG-8VJG exploitable, and should I be worried? Whether GHSA-G8FC-VRCG-8VJG 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-G8FC-VRCG-8VJG 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-G8FC-VRCG-8VJG? Upgrade
github.com/edgelesssys/constellation/v2to 2.16.3 or later.