Yesterday it was Pillow; today it's the Node side of the same problem. sharp — the image library sitting under most Node resize, convert, and thumbnail pipelines, including plenty of vision and multimodal preprocessing — ships 0.35.0 to bundle a patched libvips and close four inherited memory-safety bugs (7.0) that fire on untrusted image input. The highest score on the board, though, is @sigstore/oci at 9.6: a credential-confusion critical in the registry client behind sigstore-js that can hand your registry tokens to a look-alike registry, fixed in 0.7.1. And fast-xml-parser patches a parser denial-of-service (8.7) in 5.10.1. All three have a fixed release.

Worth your morning

sharp — the Node companion to yesterday's Pillow. GHSA-f88m-g3jw-g9cj (7.0) isn't a flaw in sharp itself but in the libvips it bundles: four CVEs (CVE-2026-33327, -33328, -35590, -35591) in image decoding that a malicious file can trip during processing. sharp 0.35.0 ships the fixed libvips 8.18.3. If any part of your pipeline resizes, converts, or thumbnails images you didn't create — user uploads, scraped media, multimodal inputs — that's today's version check.

@sigstore/oci — the critical, and it's about your credentials. CVE-2026-59891 (9.6) is a credential-confusion bug in the OCI-registry client used by sigstore-js: destination references were matched by substring instead of exact hostname, so credentials from your Docker config could be sent to a registry that merely resembled the intended one — exposing long-lived registry tokens. An exact-hostname check that had been settling for close enough. 0.7.1 tightens the match. If you sign or push artifacts with sigstore tooling in CI, upgrade; and if a vulnerable version ran against a private registry, treat those tokens as ones to rotate.

fast-xml-parser — the transitive dependency doing the heavy lifting. GHSA-8r6m-32jq-jx6q (8.7) is a denial-of-service: repeated DOCTYPE declarations reset the parser's entity-expansion guard, so a small crafted document can exhaust CPU and memory and take the process down. 5.10.1 restores the limit. It rides deep as a transitive dependency across the JS SDK world — run npm ls fast-xml-parser to find where it landed.

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