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
    Ping2Prompt story card: Traefik 2.11.61 fixes a resource leak that lets attackers exhaust memory. High, Traefik.

    Traefik 2.11.61 fixes a resource leak that lets attackers exhaust memory

    Traefik

    Traefik leak lets unauthenticated users exhaust resources

    Traefik has a resource leak, tracked as CVE-2026-130732, that lets unauthenticated attackers exhaust memory, file descriptors and backend connections. NVD rates it 8.7 (High) on CVSS 4.0, with the impact falling on availability. The exploitation status is unknown (the sources do not say), so treat the update as urgent.

    One backend transport per NTLM or Negotiate connection

    An attacker sends requests with an Authorization header using the NTLM or Negotiate scheme and opens many short-lived connections. Each such connection allocates a dedicated backend transport that is never released, so resources pile up until the proxy runs short. No login is needed to trigger it.

    Traefik 2.11.58 up to before 2.11.61 is affected

    The affected range is Traefik from 2.11.58 up to, but not including, 2.11.61. Check your running version; if it falls in that range, you are exposed. The NVD record is still marked "Awaiting Analysis" and points to the Traefik GitHub advisory GHSA-xv5x-242w-7hf7.

    Upgrade Traefik to 2.11.61 or later

    The affected range ends before 2.11.61, so upgrade to 2.11.61 or later. Read the GitHub advisory GHSA-xv5x-242w-7hf7 before you deploy, to confirm the fixed version.

    What the Traefik record leaves out

    The record does not state a fixed version outright, give a workaround, or list disclosure or patch dates. It also does not say whether Traefik 3.x is affected.

    Product Affected Fixed
    Traefik 2.11.x 2.11.58 up to before 2.11.61 2.11.61 (implied by the affected range)

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion