# CVE-2025-32793: Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters > A race condition in Cilium allows unencrypted packets from terminating endpoints to bypass WireGuard encryption, exposing sensitive data. - **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Apr 2025 - **Updated:** 21 Apr 2025 - **Also known as:** BIT-cilium-2025-32793, BIT-cilium-operator-2025-32793, BIT-hubble-relay-2025-32793, GHSA-5vxx-c285-pcq4, GO-2025-3635, MINI-3383-pg63-cpc2, MINI-9hfh-g8h3-9ccw, MINI-m8v7-f35r-gr2c, MINI-mjcj-qp94-cjx3 ## What is CVE-2025-32793? CVE-2025-32793 is a medium-severity vulnerability in cilium, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Versions 1.15.0 to 1.15.15, 1.16.0 to 1.16.8, and 1.17.0 to 1.17.2, are vulnerable when using Wireguard transparent encryption in a Cilium cluster, packets that originate from a terminating endpoint can leave the source node without encryption due to a race condition in how traffic is processed by Cilium. This issue has been patched in versions 1.15.16, 1.16.9, and 1.17.3. There are no workarounds available for this issue. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-319 (Cleartext Transmission of Sensitive Information) ## Which versions are affected by CVE-2025-32793? 10 open source packages ship an affected version, including github.com/cilium/cilium, cilium and cilium-operator. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/cilium/cilium` | Go | From 1.13.0 | 1.15.16, 1.16.9, 1.17.3 | | `github.com/cilium/cilium` | Go | From 1.13.0 | 1.15.16 | | `github.com/cilium/cilium` | Go | From 1.13.0 | 1.15.16 | | `github.com/cilium/cilium` | Go | From 1.16.0 | 1.16.9 | | `github.com/cilium/cilium` | Go | From 1.16.0 | 1.16.9 | | `github.com/cilium/cilium` | Go | From 1.17.0 | 1.17.3 | | `github.com/cilium/cilium` | Go | From 1.17.0 | 1.17.3 | | `cilium` | Bitnami | From 1.13.0 | 1.17.3 | | `cilium-operator` | Bitnami | From 1.13.0 | 1.17.3 | | `hubble-relay` | Bitnami | From 1.13.0 | 1.17.3 | Products: Cilium Cilium. ## How do I fix CVE-2025-32793? Upgrade github.com/cilium/cilium to a fixed version for your release line: 1.15.16, 1.16.9 or 1.17.3. ## Is CVE-2025-32793 being exploited? There is no known exploitation of CVE-2025-32793 in the wild and no public exploit code. ## Other vulnerabilities in cilium - [CVE-2026-49445](https://insights.sbomify.com/CVE-2026-49445/): Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access (critical 9.2) - [CVE-2022-29178](https://insights.sbomify.com/CVE-2022-29178/): Incorrect Default Permissions in Cilium (high 8.8) - [CVE-2024-28860](https://insights.sbomify.com/CVE-2024-28860/): Insecure IPsec transport encryption in Cilium (high 8.0) - [CVE-2026-41520](https://insights.sbomify.com/CVE-2026-41520/): Cillium exposes sensitive information included in the cilium-bugtool debug archive (high 7.9) - [CVE-2024-37307](https://insights.sbomify.com/CVE-2024-37307/): Cilium leaks sensitive information in cilium-bugtool (high 7.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-32793 and fix it if it is affected. What it is: CVE-2025-32793 is a medium-severity vulnerability in cilium, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-32793 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/cilium/cilium (Go): affected from 1.13.0; fixed in 1.15.16, 1.16.9, 1.17.3 - github.com/cilium/cilium (Go): affected from 1.13.0; fixed in 1.15.16 - github.com/cilium/cilium (Go): affected from 1.13.0; fixed in 1.15.16 - github.com/cilium/cilium (Go): affected from 1.16.0; fixed in 1.16.9 - github.com/cilium/cilium (Go): affected from 1.16.0; fixed in 1.16.9 - github.com/cilium/cilium (Go): affected from 1.17.0; fixed in 1.17.3 - github.com/cilium/cilium (Go): affected from 1.17.0; fixed in 1.17.3 - cilium (Bitnami): affected from 1.13.0; fixed in 1.17.3 - cilium-operator (Bitnami): affected from 1.13.0; fixed in 1.17.3 - hubble-relay (Bitnami): affected from 1.13.0; fixed in 1.17.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-32793/ (Markdown: https://insights.sbomify.com/CVE-2025-32793/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32793 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32793 - OSV: https://osv.dev/vulnerability/CVE-2025-32793 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-32793/ Summaries are generated and may contain mistakes; the official description above is the record.