Login
You're viewing the functional.cafe public feed.
  • Nov 18, 2026, 6:39 PM

    honestly at a glance this looks maybe worse than the PHPocalypse a few weeks ago

    a saving grace perhaps is that the worst of these flaws _probably_ only affects you when http2 is enabled (there’s other security fixes too though)

    anyway UPGRADE

    💬 2🔄 1⭐ 0

Replies

  • 💬 0🔄 0⭐ 0
  • Emelia/Emibecomethewaifu@tech.lgbt
    Nov 18, 2026, 6:58 PM

    @thomasfuchs The main flaw is in http2 buffer logic, so yeah, it only impacts servers with http2 enabled. The rest of them require some non-default config (most require use of proxy_pass) which mitigates things somewhat.

    That said, I've disabled http2 for the time being, and will update as soon as debian actually releases the patch... (It appears that nobody bothered to loop them in ahead of time, since there's still nothing released yet)

    💬 1🔄 1⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 19, 2026, 3:34 AM

    @becomethewaifu@tech.lgbt @thomasfuchs@hachyderm.io The Debian Sid packages are now ready, but not unstable or stable yet. If one is in a hurry, one can manually unblock the unstable version:

    # cat /etc/apt/preferences.d/nginx-cve.pref 
    Package: nginx nginx-* libpcre2-8-0
    Pin: release o=Debian,a=unstable
    Pin-Priority: 1000
    
    # Don't use Debian Unstable packages by default
    Package: *
    Pin: release o=Debian,a=unstable
    Pin-Priority: -10

    And add
    https://deb.debian.org/debian unstable main contrib to /etc/apt/sources.list.

    Now
    apt update && apt upgrade will have nginx upgraded.

    But use it at your own risk if you deploy it for Serious Business...

    💬 0🔄 1⭐ 0