### Impact When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as: - Exposing TLS secrets - Disrupting traffic in the cluster - Terminating the Envoy process This issue affects both the embedded and standalone Envoy deployment models. ### Patches This issue affects: - Cilium v1.19 between v1.19.0 and v1.19.1 inclusive - Cilium v1.18 between v1.18.0 and v1.18.7 inclusive - All versions of Cilium prior to v1.17.14 This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in: - Cilium v1.19.2 - Cilium v1.18.8 - Cilium v1.17.14 ### Workarounds There is no known workaround to this issue. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to [moemen](https://github.com/moemen) for reporting the issue and [0xch4z](https://github.com/0xch4z) for their work on triaging and remediating this issue. ### For more information If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/). If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.
### Impact When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as: - Exposing TLS secrets - Disrupting traffic in the cluster - Terminating the Envoy process This issue affects both the embedded and standalone Envoy deployment models. ### Patches This issue affects: - Cilium v1.19 between v1.19.0 and v1.19.1 inclusive - Cilium v1.18 between v1.18.0 and v1.18.7 inclusive - All versions of Cilium prior to v1.17.14 This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in: - Cilium v1.19.2 - Cilium v1.18.8 - Cilium v1.17.14 ### Workarounds There is no known workaround to this issue. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to [moemen](https://github.com/moemen) for reporting the issue and [0xch4z](https://github.com/0xch4z) for their work on triaging and remediating this issue. ### For more information If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/). If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.
Update github.com/cilium/cilium to 1.19.2; github.com/cilium/cilium to 1.18.8; github.com/cilium/cilium to 1.17.14 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanCilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access affects github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go). Severity is critical. ### Impact When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as: - Exposing TLS secrets - Disrupting traffic in the cluster - Terminating the Envoy process This issue affects both the embedded and standalone Envoy deployment models. ### Patches This issue affects: - Cilium v1.19 between v1.19.0 and v1.19.1 inclusive - Cilium v1.18 between v1.18.0 and v1.18.7 inclusive - All versions of Cilium prior to v1.17.14 This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in: - Cilium v1.19.2 - Cilium v1.18.8 - Cilium v1.17.14 ### Workarounds There is no known workaround to this issue. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to [moemen](https://github.com/moemen) for reporting the issue and [0xch4z](https://github.com/0xch4z) for their work on triaging and remediating this issue. ### For more information If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/). If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/cilium/ciliumgo | >=1.19.0,<1.19.2 | 1.19.2 |
| github.com/cilium/ciliumgo | >=1.18.0,<1.18.8 | 1.18.8 |
| github.com/cilium/ciliumgo | <1.17.14 | 1.17.14 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate github.com/cilium/cilium to 1.19.2; github.com/cilium/cilium to 1.18.8; github.com/cilium/cilium to 1.17.14 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanCilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access affects github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go). Severity is critical. ### Impact When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as: - Exposing TLS secrets - Disrupting traffic in the cluster - Terminating the Envoy process This issue affects both the embedded and standalone Envoy deployment models. ### Patches This issue affects: - Cilium v1.19 between v1.19.0 and v1.19.1 inclusive - Cilium v1.18 between v1.18.0 and v1.18.7 inclusive - All versions of Cilium prior to v1.17.14 This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in: - Cilium v1.19.2 - Cilium v1.18.8 - Cilium v1.17.14 ### Workarounds There is no known workaround to this issue. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to [moemen](https://github.com/moemen) for reporting the issue and [0xch4z](https://github.com/0xch4z) for their work on triaging and remediating this issue. ### For more information If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/). If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/cilium/ciliumgo | >=1.19.0,<1.19.2 | 1.19.2 |
| github.com/cilium/ciliumgo | >=1.18.0,<1.18.8 | 1.18.8 |
| github.com/cilium/ciliumgo | <1.17.14 | 1.17.14 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard