Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in

    Topic

    Docker

    6 stories · RSS for this tag · All series · Latest

    1. Vulnerability Critical Dokploy 0.31.0 fixes critical flaw giving read-only members host access CVE-2026-129316, rated 9.9 critical by NVD, lets a read-only Dokploy member reach other services' containers, get a root shell in the panel container and compromise the host. Exploitation status is unknown. Upgrade to Dokploy 0.31.0.
    2. Vulnerability High Portainer 2.45.4 fixes network access bypass for Standard Users Portainer skipped network resource control when workloads were created on a named network, letting Standard Users join other teams' private Docker networks if they know the name or ID. Update to 2.45.4, 2.39.9 or 3.1.0.
    3. Vulnerability Critical MyMangaDB 2.7.2 fixes critical unauthenticated database export and import flaws MyMangaDB versions before 2.7.2 have two unauthenticated flaws, CVE-2026-77297 (CVSS 9.3) and CVE-2026-77295 (8.7), letting anyone export or replace the database, including an admin account. Exploitation status is unknown. Upgrade to 2.7.2.
    4. Vulnerability High containerd 2.2.10, 2.3.7 and 2.4.2 fix a daemon crash from crafted images CVE-2026-95839, a 7.1 HIGH flaw in containerd, lets a crafted image trigger an unrecovered panic that crashes the daemon, repeatedly on Kubernetes nodes via kubelet retries. Update to 2.2.10, 2.3.7 or 2.4.2, prioritising worker nodes.
    5. Release Docker Engine 29.10.0 changes how loopback registries are treated as insecure Docker Engine 29.10.0 no longer treats loopback addresses as insecure when insecure-registries or --insecure-registry is set, so local registry pulls and pushes may fail. Use trusted TLS or list addresses like localhost:5000 before upgrading.
    6. Friday Footgun Docker published ports bypass ufw rules: check yours before the weekend Docker's docs say publishing a container port with -p or --publish diverts its traffic before ufw's settings apply, so the firewall is effectively ignored. Check which containers publish ports, drop unneeded ones, and test from a second machine.