GHSA-g8fc-vrcg-8vjg — v2
GHSA-g8fc-vrcg-8vjg is a security vulnerability in github.com/edgelesssys/constellation/v2. A fix is available for github.com/edgelesssys/constellation/v2 — see the affected versions and patch details below.
Constallation has pods exposed to peers in VPC
Real-World Exposure
github.com/edgelesssys/constellation/v2Real-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
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.
Patches
The issue has been patched in v2.16.3.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/edgelesssys/constellation/v2 | all versions | 2.16.3go get github.com/edgelesssys/constellation/v2@v2.16.3 |
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/constellation/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/edgelesssys/constellation/v2 to 2.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8fc-vrcg-8vjg 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-g8fc-vrcg-8vjg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g8fc-vrcg-8vjg. 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-g8fc-vrcg-8vjg in your dependencies?
O3 Security finds GHSA-g8fc-vrcg-8vjg across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.