Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-2h44-x2wx-49f4

Potential HTTP policy bypass when using header rules in Cilium

CVSS 2.6 LowEPSS 0.0066 · 51st percentile

Published by the GitHub Advisory Database at 22 May 2023, 20:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo<1.11.16 || >=1.12.0, <1.12.9 || >=1.13.0, <1.13.21.11.16, 1.12.9, 1.13.2
Identifiers
GHSA-2h44-x2wx-49f4 · BIT-cilium-2023-30851 · BIT-cilium-operator-2023-30851 · BIT-cilium-proxy-2023-30851 · BIT-hubble-2023-30851 · BIT-hubble-relay-2023-30851 · BIT-hubble-ui-2023-30851 · BIT-hubble-ui-backend-2023-30851 · CVE-2023-30851 · GO-2023-1785
Weakness (CWE)
CWE-693
Tags
Published
22 May 2023
Updated
10 Sept 2026

Machine-written summary

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

Cilium (github.com/cilium/cilium) versions before 1.11.16, from 1.12.0 before 1.12.9, and from 1.13.0 before 1.13.2 are affected. The issue only arises when an HTTP policy applies to multiple endpoints and an allow-all rule covers just one of them, which can let a wildcard rule bypass HTTP policies. Upgrade to 1.11.16, 1.12.9, 1.13.2 or later; as a workaround, rewrite HTTP rules so each endpoint is defined separately.

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
2.6 Low 3.1 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0066, the 51st percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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