Advisory record · GHSA-vwf8-q6fw-4wcm

Cilium leaks information via incorrect ReferenceGrant update logic in Gateway API

CVSS 5.4 MediumEPSS 0.0057 · 48th percentile

Published by the GitHub Advisory Database at 16 Aug 2024, 18:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.16.0, <1.16.1 || >=1.15.0, <1.15.81.16.1, 1.15.8
Identifiers
GHSA-vwf8-q6fw-4wcm · BIT-cilium-2024-42486 · BIT-cilium-operator-2024-42486 · BIT-hubble-relay-2024-42486 · CVE-2024-42486 · GO-2024-3074
Weakness (CWE)
CWE-200
Published
16 Aug 2024
Updated
10 Sept 2026

Machine-written summary

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

Cilium (Go module github.com/cilium/cilium) versions 1.15.0 through 1.15.7 and 1.16.0 are affected. After a ReferenceGrant is revoked, Gateway resources in Cilium's Gateway API controller can keep using secrets in other namespaces because the change is not propagated immediately, so an attacker with a Gateway that has such access may still establish sessions with those secrets. Upgrade to 1.15.8 or 1.16.1. As a workaround, add a label or make another change to the related Gateway, HTTPRoute, GRPCRoute, or TCPRoute resources to trigger a ReferenceGrant reconciliation.

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

Timeline

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