Policy bypass for Host Firewall policy due to race condition in Cilium agent

Exploitation

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

CVSS

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

EPSS

• CVE-2024-42488: 0.50% estimated exploitation activity in the next 30 days; percentile 42.88 (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 A race condition in the Cilium agent can cause the agent to ignore labels that should be applied to a node. This could in turn cause CiliumClusterwideNetworkPolicies intended for nodes with the ignored label to not apply, leading to policy bypass. Patches This issue was fixed in https://github.com/cilium/cilium/pull/33511. This issue affects: - All versions of Cilium before v1.14.14 - Cilium v1.15 between v1.15.0 and v1.15.7 inclusive This issue has been patched in: - Cilium v1.14.14 - Cilium v1.15.8 Workarounds As the underlying issue depends on a race condition, users unable to upgrade can restart the Cilium agent on affected nodes until the affected policies are confirmed to be working as expected. Acknowledgements The Cilium community has worked together with members of Google and Isovalent to prepare these mitigations. Special thanks to @skmatti for raising and resolving this issue. For more information If you have any questions or comments about this advisory, please…

Published by the source

15 Aug 2024, 21:43 UTC

Last modified by the source

15 Aug 2024, 22:35 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q7w8-72mr-vpgw

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

# Patch Next advisory brief: CVE-2024-42488

Advisory: Policy bypass for Host Firewall policy due to race condition in Cilium agent
IDs: CVE-2024-42488, GHSA-q7w8-72mr-vpgw
Record: https://patchnext.com/advisories/cve-2024-42488 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
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.15.8, 1.14.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected < 1.14.14; >= 1.15.0, < 1.15.8; fixed in 1.14.14, 1.15.8

## 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-q7w8-72mr-vpgw (GitHub-reviewed advisory GHSA-q7w8-72mr-vpgw lists affected ranges: Go github.com/cilium/cilium >=0 =1.15.0 <1.15.8)

Commands are suggestions: review each one before running it.