What Changed This Week for Server Owners: 20 November 2026

Update nginx this week: a batch of ten fixes landed on 18 November, and the same HTTP/2 bug reaches Synology NAS boxes too. Docker 29.10 also changes how local registries are trusted, and an old Synology flaw and a LiteLLM bug are now being exploited.
Patch now
nginx 1.30.7 and 1.31.9 fix ten vulnerabilities
On 18 November the nginx project released 1.30.7 (stable) and 1.31.9 (mainline) with fixes for ten CVEs. The headline one is CVE-2026-123007, memory corruption in HTTP/2 flow control that researchers have nicknamed NGINX2Root. The rest cover use-after-free bugs in the resolver, HTTP/2, HTTP/3 and mail proxy, plus problems with PROXY protocol v2, alias with try_files, and stream module certificate checks.
Why it matters: nginx sits in front of a huge number of home lab and small business services, often as the reverse proxy facing the internet.
What to do: update to 1.30.7 or 1.31.9, or your distro’s patched package (backports may keep the old version string, so check the package changelog). If you can’t patch straight away, turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 only, not the others.
Synology DSM: NGINX2Root reaches your NAS
Synology published advisory SA-26:20 on 19 November, rating the nginx HTTP/2 bug (CVE-2026-123007) as critical for DSM, BeeStation OS and DSM Enterprise. Fixed builds DSM 7.4.1-90080-2 and DSM 7.3.2-86009-6 are scheduled for release by 20 November. Older branches (DSM 7.1, 7.2.1 and 7.2.2) are still listed as ongoing, and SRM routers are not affected.
Why it matters: this one is in DSM itself, so a NAS reachable from the internet is exposed whether or not you run your own nginx.
What to do: install 7.4.1-90080-2 or 7.3.2-86009-6 as soon as they appear. Until then, Synology’s advice is to disable HTTP/2 under Control Panel, Network, Connectivity. If you’re on DSM 7.2.x, Synology recommends moving to 7.3.2-86009-6 or later.
Synology DSM: a 2024 bug is now on CISA’s exploited list
On 18 November CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities catalogue. It is an unauthenticated remote code execution bug in DSM’s system plugin daemon, fixed in DSM 7.2.2-72806-1 and 7.2.1-69057-6 (BeeStation OS 1.1-65374). Being on CISA’s list means it is being used in real attacks.
Why it matters: a NAS that has sat unpatched since 2024 is now a live target, and it usually holds your backups.
What to do: check Control Panel, Update and Restore. If you’re on anything older than the builds above, update now, and while you’re there move to a current release for the NGINX2Root fix too.
New releases
Tailscale: opt-in netmap caching
In a 17 November post, Tailscale explained client-side netmap caching: the client keeps a copy of your tailnet map on disk, so it starts faster and can still reach peers when the coordination server is unreachable. It’s off by default, needs clients on 1.104 or later, and isn’t available on Android or iOS yet. You turn it on with the cache-network-maps node attribute in your policy file.
Why it matters: if Tailscale is how you reach your home lab, caching keeps existing connections working through a control plane outage or a flaky link.
What to do: nothing required. If you try it, Tailscale’s docs suggest leaving it off on subnet routers, exit nodes and small devices to save disk writes.
Changes and deprecations
Docker Engine 29.10.0 changes local registry trust
Docker Engine 29.10.0 came out on 16 November with a flagged potential breaking change. If you set insecure-registries yourself (in daemon.json or with --insecure-registry), loopback addresses such as localhost:5000 are no longer treated as insecure automatically. If you never set that option, nothing changes. The release also updates runc to v1.5.3 and BuildKit to v0.35.0.
Why it matters: a local registry on plain HTTP is a common home lab setup, and pushes or pulls to it may start failing after the upgrade.
What to do: before upgrading, check daemon.json. If you have an insecure-registries list and use a local registry, add its address (for example localhost:5000) or give it a trusted TLS certificate. Our Docker on Ubuntu guide shows where the daemon config lives.
Using AI safely
LiteLLM’s guardrail tester is being exploited
CISA’s 18 November update also added CVE-2026-40217 in LiteLLM, the popular proxy for routing requests to AI models. The bug lets a caller escape the sandbox on the /guardrails/test_custom_code endpoint and run code on the server. Zenity Labs saw hundreds of attempts against a honeypot, each one guessing a master key such as sk-1234, and notes the official Docker image runs as root.
Why it matters: a self-hosted LiteLLM proxy holds API keys for every model provider you use, and a weak master key plus this bug hands an attacker the box.
What to do: update to the latest LiteLLM release (Zenity says 1.83.10 fixed it), change any default or guessable master key, keep the admin endpoints off the internet, and run the container as a non-root user.
Source: Zenity Labs and SecurityOnline
That’s the week. If something here affects you and you’d like a full guide, say hello on LinkedIn.