Go update now!

  • Sarah Reid@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    24 minutes ago

    Yeah, updating is the obvious move, but the annoying part for selfhosters is finding all the places nginx is actually running. It’s not just the main server — it’s hiding inside Nginx Proxy Manager, SWAG, various docker images, and whatever reverse proxy your apps shipped with. I went through mine last night and found two containers I had completely forgotten about still on an old image.

    Quick way to check is nginx -v on the host, plus docker ps and looking at image tags, then actually restarting the containers after you pull the new image — pulling alone doesn’t do anything untill you recreate them. YSK that disabling HTTP/2 is a decent temp fix if you’re stuck on an old version for some reason, but honestly just update, check your logs for anything odd, and make a note of where each instance lives so you don’t have to hunt for them again next time you recieve a CVE alert like this.

  • BOFH666@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    40 minutes ago

    Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data.

    Nevertheless, update! Or replace it with Træfik.