Advisory record · GHSA-3fcv-jvfp-m4q9

Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access

CVSS 9.2 CriticalCriticalEPSS 0.0017 · 5th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 Jul 2026, 17:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.19.0, <1.19.2 || >=1.18.0, <1.18.8 || <1.17.141.19.2, 1.18.8, 1.17.14
Identifiers
GHSA-3fcv-jvfp-m4q9 · BIT-cilium-2026-49445 · BIT-cilium-operator-2026-49445 · BIT-hubble-relay-2026-49445 · CVE-2026-49445 · GO-2026-5905
Weakness (CWE)
CWE-732 · CWE-862
Published
6 Jul 2026
Updated
20 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cilium (github.com/cilium/cilium) versions before 1.17.14, 1.18.0 through 1.18.7, and 1.19.0 through 1.19.1 are affected. When Cilium L7 functionality is enabled, the Envoy instance creates a world-accessible socket on cluster nodes, so a local attacker can reach Envoy admin endpoints and potentially expose TLS secrets, disrupt cluster traffic, or terminate Envoy. Upgrade to 1.17.14, 1.18.8, or 1.19.2; the source lists no workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.2 Critical 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 5th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.