Advisory record · GHSA-h78m-j95m-5356

Cilium has an information leakage via insecure default Hubble UI CORS header

CVSS 6.5 MediumEPSS 0.0049 · 42nd percentile

Published by the GitHub Advisory Database at 22 Jan 2025, 18:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.14.0, <1.14.19 || >=1.15.0, <1.15.13 || >=1.16.0, <1.16.61.14.19, 1.15.13, 1.16.6
Identifiers
GHSA-h78m-j95m-5356 · BIT-cilium-2025-23047 · BIT-cilium-operator-2025-23047 · BIT-hubble-relay-2025-23047 · CVE-2025-23047 · GO-2025-3416
Weakness (CWE)
CWE-200
Published
22 Jan 2025
Updated
10 Sept 2026

Machine-written summary

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

Cilium versions 1.14.0 to before 1.14.19, 1.15.0 to before 1.15.13, and 1.16.0 to before 1.16.6 are affected. An insecure default Access-Control-Allow-Origin header in Hubble UI, deployed via the Cilium CLI or Helm chart, lets a malicious web page that a logged-in user visits read cluster configuration details such as node names, IP addresses, and workload and networking metadata. Upgrade to Cilium 1.14.19, 1.15.13, 1.16.6 or later. If you deploy Hubble UI with the Helm chart, you can remove the CORS headers from the chart template instead.

Written 1 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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 42nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 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.