A loud morning after a quiet week. LightRAG — the open-source retrieval-augmented-generation server — ships 1.5.4 to close two criticals at once, both scored 9.3: a hardcoded JWT secret that lets an unauthenticated caller reach admin operations, and a CORS setup that pairs a wildcard origin with credentials, so any site an authenticated user visits can fire requests at their instance. If you run LightRAG's API server, that's the upgrade to make today. Below it, Pillow's coordinated 12.3.0 release clears a batch of memory-corruption bugs that reach anyone with a vision or multimodal pipeline, node-tar patches a critical decompression DoS (7.5.19), and axios closes a proxy-leak high (1.18.0). Everything here has a fixed release.

Worth your morning

LightRAG — two criticals, one release. CVE-2026-61740 (9.3) is an authentication bypass: the API server shipped with a hardcoded default JWT secret and an auth-status endpoint outside the guard, so a caller who never authenticated can reach document deletion, uploads, cache clearing, and knowledge-graph edits. CVE-2026-61736 (9.3) is the companion: a CORS policy that returns a wildcard origin alongside Allow-Credentials, which lets any page an authenticated user opens make credentialed calls to their LightRAG instance and read or destroy its data. Both close in 1.5.4. If the server is exposed at all, upgrade and keep it off untrusted networks; if a vulnerable version was reachable, treat its documents and graph as having been readable.

Pillow — the coordinated release you apply on sight. 12.3.0 fixes a stack of image-handling flaws at once: heap out-of-bounds writes via coordinate overflow in Image.paste() / crop() (CVE-2026-59199, 7.5) and in ImageCmsTransform and RankFilter, several decompression-bomb-check bypasses, and a command injection in WindowsViewer.get_command() via unescaped filenames (CVE-2026-55798). Pillow sits under most vision and multimodal preprocessing, so if you process images anywhere near untrusted input, 12.3.0 is a version check worth doing today.

node-tar and axios — the transitive dependencies you didn't pick. CVE-2026-59873 (9.2) is a decompression DoS in node-tar: no upper bound on decompressed volume, so a small archive expands to exhaust disk and CPU; 7.5.19 is the floor, and companion advisories for a negative-size infinite loop and a PAX path crash close in the same release. For axios, GHSA-gcfj-64vw-6mp9 (8.3) can route a plaintext HTTP request through an attacker-controlled proxy — leaking Authorization headers and body — but only where prototype pollution already exists and an interceptor returns a plain-object config copy; 1.18.0 (or 0.33.0 on the old line) fixes it, alongside a batch of moderate axios issues in the same release. Both packages ride in deep as transitive dependencies — run npm ls tar and npm ls axios to see where.

vLLM — a third reason for a release you may already have. CVE-2026-55514 (7.1) is a crash-DoS: a prompt-embeds payload to an M-RoPE model trips an assertion and takes the server down. It's fixed in 0.24.0 — the same release the 19th's digest flagged for a ReDoS and a token-reinjection DoS — so if you upgraded then, you're already covered. If you didn't, that's now three availability bugs behind one version bump.

Quiet on the .NET, NuGet, Azure, PrimeNG, and Angular side — nothing new has cleared the bar since July's servicing release on the 14th.