p PatchFirst

PatchFirst · Latest vulnerabilities

docker engine 26.0.0: known vulnerabilities

Known vulnerabilities affecting docker engine 26.0.0: 3. Compare the fixes below with your installed release.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 3

  1. CVE-2026-92543

    High · CVSS 7.6EPSS 0.09%Fix available

    Docker Engine insecure-registry fallback via malicious DNS responses

    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.

    docker engineContainers
    • Update to 29.8.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  2. CVE-2026-92542

    Medium · CVSS 6.9EPSS 0.07%Fix available

    Blind VXLAN injection into encrypted overlay networks from cluster peer

    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: - UDP datagram - Destination port is the Swarm data-path port - Datagram starts with a VXLAN header for the VNI of an encrypted overlay network which any running container on the node is connected to

    docker engineContainers
    • Update to 29.8.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  3. CVE-2026-17106

    High · CVSS 7.1EPSS 0.44%Public exploitFix available

    Tar extraction in moby/go-archive can write outside the destination directory via link following

    The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.

    docker engineContainers
    • Update to 29.7.0
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →