{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "Docker Engine: all CVE events",
 "home_page_url": "https://patchwire.jonathanross.dev/products/docker--docker-engine/",
 "feed_url": "https://patchwire.jonathanross.dev/feeds/products/docker--docker-engine/all.json",
 "authors": [
  {
   "name": "Patchwire"
  }
 ],
 "language": "en",
 "items": [
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-92543/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-92543/",
   "title": "CVE-2026-92543 disclosed",
   "content_text": "Docker Engine classifies a registry hostname as insecure using an any-match DNS check. loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP fallback for the registry connection.",
   "date_published": "2026-10-07T16:44:21Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-92543/fixed/chainguard",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-92543/",
   "title": "CVE-2026-92543 fixed in Chainguard",
   "content_text": "Fixed versions: py3-docker 0, py3.10-docker 0, py3.11-docker 0, py3.12-docker 0, py3.13-docker 0.",
   "date_published": "2026-10-07T16:44:21Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-92543/fixed/wolfi",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-92543/",
   "title": "CVE-2026-92543 fixed in Wolfi",
   "content_text": "Fixed versions: py3-docker 0, py3.10-docker 0, py3.11-docker 0, py3.12-docker 0, py3.13-docker 0.",
   "date_published": "2026-10-07T16:44:21Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-92542/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-92542/",
   "title": "CVE-2026-92542 disclosed",
   "content_text": "The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets the following criteria:\n\n- UDP datagram\n- Destination port is the Swarm data-path port\n- Datagram starts with a VXLAN header for the VNI of an encrypted overlay network which any running container on the node is connected to",
   "date_published": "2026-10-07T16:42:20Z"
  }
 ]
}