CVE-2025-23047: GO-2025-3416 - Cilium has an information leakage via insecure default Hubble UI CORS header in github.com/cilium/cilium

CVE-2025-23047 · Severity: low · CVSS 3.1 · Published 2025-01-28

Cilium has an information leakage via insecure default Hubble UI CORS header in github.com/cilium/cilium

Technologies: github.com/cilium/cilium (Go). Vendors: Go.

Quick answers

Is CVE-2025-23047 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-23047 being exploited in the wild.
How severe is CVE-2025-23047?
Low severity, with a CVSS score of 3.1, published 28 January 2025.
Which products and versions are affected?
github.com/cilium/cilium (Go) SEMVER:introduced=1.14.0,fixed=1.14.19, SEMVER:introduced=1.14.0,fixed=1.14.19,introduced=1.15.0,fixed=1.15.13,introduced=1.16.0,fixed=1.16.6.
Is there a fix for CVE-2025-23047?
Yes. github.com/cilium/cilium (Go): upgrade to 1.14.19, 1.16.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-23047?
Check whether you run github.com/cilium/cilium (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/cilium/cilium (Go): upgrade to 1.14.19, 1.16.6 or later
    go get github.com/cilium/cilium@v1.16.6

Affected products

  • github.com/cilium/cilium (Go) SEMVER:introduced=1.14.0,fixed=1.14.19, SEMVER:introduced=1.14.0,fixed=1.14.19,introduced=1.15.0,fixed=1.15.13,introduced=1.16.0,fixed=1.16.6

Identifiers

  • CVE-2025-23047
  • GHSA-h78m-j95m-5356
  • GO-2025-3416

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.