{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "introduced": "1.19.0"
              },
              {
                "fixed": "1.19.5"
              }
            ],
            "source": [
              "AFFECTED_FIELD",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "7c6667e1e707d7f39a4af3409c2a9ebea2917d32"
            },
            {
              "fixed": "1c84ae3b58a7cd54f7ee355e6c524c82f620eae8"
            },
            {
              "fixed": "bacea640404c0805c23515353dc1681c5bf35171"
            },
            {
              "fixed": "20eaccfef029cb046d70219717fb6dbbdf27a59f"
            }
          ],
          "repo": "https://github.com/cilium/cilium",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-fm8w-2m5w-9j7r"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-863"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/56xxx/CVE-2026-56743.json"
  },
  "details": "Cilium is a networking, observability, and security solution. From 1.19.0 to 1.19.4, standard Kubernetes NetworkPolicy specifications using CIDR-based ipBlock rules without pod or namespace selectors erroneously generate a wildcard namespace allow rule when Cilium is configured with a custom clusterName rather than the default any value. The parser incorrectly instantiates a pod selector on selectorless peer definitions, allowing traffic from other workloads in the same namespace as the subject of the policy. This issue is fixed in version 1.19.5.",
  "id": "CVE-2026-56743",
  "modified": "2026-07-18T03:41:53.399582995Z",
  "published": "2026-07-15T19:15:30.924Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/cilium/cilium/releases/tag/v1.19.5"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/56xxx/CVE-2026-56743.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/cilium/cilium/security/advisories/GHSA-fm8w-2m5w-9j7r"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56743"
    },
    {
      "type": "FIX",
      "url": "https://github.com/cilium/cilium/commit/1c84ae3b58a7cd54f7ee355e6c524c82f620eae8"
    },
    {
      "type": "FIX",
      "url": "https://github.com/cilium/cilium/commit/bacea640404c0805c23515353dc1681c5bf35171"
    },
    {
      "type": "FIX",
      "url": "https://github.com/cilium/cilium/pull/46305"
    },
    {
      "type": "FIX",
      "url": "https://github.com/cilium/cilium/pull/46456"
    }
  ],
  "schema_version": "1.8.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match"
}