Skip to content
Fencer Intel
medium 5.3

CVE-2025-23028 json

DoS in Cilium agent DNS proxy from crafted DNS responses

published last yr. modified last mo. also BIT-cilium-2025-23028 , BIT-cilium-operator-2025-23028 , BIT-hubble-relay-2025-23028 , EUVD-2025-0150 , GHSA-9m5p-c77c-f9j7 , GO-2025-3415

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. A denial of service vulnerability affects versions 1.14.0 through 1.14.7, 1.15.0 through 1.15.11, and 1.16.0 through 1.16.4. In a Kubernetes cluster where Cilium is configured to proxy DNS traffic, an attacker can crash Cilium agents by sending a crafted DNS response to workloads from outside the cluster. For traffic that is allowed but without using DNS-based policy, the dataplane will continue to pass traffic as configured at the time of the DoS. For workloads that have DNS-based policy configured, existing connections may continue to operate, and new connections made without relying on DNS resolution may continue to be established, but new connections which rely on DNS resolution may be disrupted. Any configuration changes that affect the impacted agent may not be applied until the agent is able to restart. This issue is fixed in Cilium v1.14.18, v1.15.12, and v1.16.5. No known workarounds are available.

Patch / fix

  • go github.com/cilium/cilium 1.14.18, 1.15.12, 1.16.5
  • bitnami cilium 1.16.5
  • bitnami cilium-operator 1.16.5
  • bitnami hubble-relay 1.16.5
  • cilium cilium 1.14.18, 1.15.12, 1.16.5
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250128T150132-150000.1.29.1

suse advisories SUSE-SU-2025:0297-1

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250128T150132-1.1

opensuse advisories openSUSE-SU-2025:14710-1

Is CVE-2025-23028 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
>=1.14.0, <1.14.18
>=1.15.0, <1.15.12
>=1.16.0, <1.16.5
1.14.18
1.15.12
1.16.5
bitnami cilium
>=1.15.4, <1.16.5
1.16.5
bitnami cilium-operator
>=1.15.4, <1.16.5
1.16.5
bitnami hubble-relay
>=1.14.0, <1.16.5
1.16.5

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.