Advisory record · GHSA-pwqm-x5x6-5586

Cilium has insecure IPsec transport encryption

CVSS 8.0 HighEPSS 0.0017 · 6th percentile

Published by the GitHub Advisory Database at 28 Mar 2024, 17:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.4.0, <1.13.14 || >=1.14.0, <1.14.9 || >=1.15.0, <1.15.31.13.14, 1.14.9, 1.15.3
Identifiers
GHSA-pwqm-x5x6-5586 · BIT-cilium-2024-28860 · BIT-cilium-operator-2024-28860 · BIT-cilium-proxy-2024-28860 · BIT-hubble-2024-28860 · BIT-hubble-relay-2024-28860 · BIT-hubble-ui-2024-28860 · BIT-hubble-ui-backend-2024-28860 · CVE-2024-28860 · GO-2024-2666
Weakness (CWE)
CWE-326
Published
28 Mar 2024
Updated
10 Sept 2026

Machine-written summary

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

Cilium versions from 1.4.0 up to but not including 1.13.14, 1.14.9 and 1.15.3 are affected when IPsec transparent encryption is enabled. A man-in-the-middle attacker on the network can mount chosen plaintext, key recovery and replay attacks because multiple nodes share the same key, which causes ESP sequence number collisions. Upgrade to Cilium 1.13.14, 1.14.9, 1.15.3 or later, then perform the key rotation described in the Cilium IPsec documentation; no workaround is listed.

Written 2 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
8.0 High 3.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 6th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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