Unencrypted traffic between pods when using Wireguard and an external kvstore

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2024-25631: 0.20% estimated exploitation activity in the next 30 days; percentile 9.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact For Cilium users who have enabled an external kvstore and Wireguard transparent encryption, traffic between pods in the affected cluster is not encrypted. Patches This issue affects Cilium v1.14 before v1.14.7. This issue has been patched in Cilium v1.14.7. Workarounds There is no workaround to this issue - affected users are encouraged to upgrade. Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @giorio94 and @gandro for their work on triaging and remediating this issue. For more information If you have any questions or comments about this advisory, please reach out on Slack. If you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list at security@cilium.io. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and your report will be treated as top priority.

Published by the source

20 Feb 2024, 23:45 UTC

Last modified by the source

21 Mar 2026, 05:27 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x989-52fc-4vr4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25631

Advisory: Unencrypted traffic between pods when using Wireguard and an external kvstore
IDs: CVE-2024-25631, GHSA-x989-52fc-4vr4
Record: https://patchnext.com/advisories/cve-2024-25631 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cilium/cilium 1.14.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected >= 1.14.0, < 1.14.7; fixed in 1.14.7

## Suggested inspection (read-only)
- Go github.com/cilium/cilium: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cilium/cilium.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x989-52fc-4vr4 (GitHub-reviewed advisory GHSA-x989-52fc-4vr4 lists affected ranges: Go github.com/cilium/cilium >=1.14.0 <1.14.7)

Commands are suggestions: review each one before running it.