(a) This is the x/net/html release pre-announced for 10-27. CVE-2026-78661 (GO-2026-6860, #82224): html.Parse/ParseFragment take quadratic time when coalescing adjacent text nodes, so a long input of repeated a</x> runs is enough. CVE-2026-97045 (GO-2026-6866, #82622): html.Render checks whether a text node's ancestors make it literal, but it stopped at the nearest foreign (SVG/MathML) ancestor. A subtree fostered under <mtext> via <mglyph>/<malignmark> therefore re-parses in a different namespace. That's the classic parseβrenderβparse mutation-XSS gap for HTML sanitizers. v0.62.0 also carries last week's ipv4/ipv6 bounds fixes. The x/idna Punycode fix (#82374) is still not in it. (b) go-jose GHSA-mgcc-cww5-fp2q (CVE-2026-116587, high): JWK parsing passes an unbounded RSA modulus and primes to crypto/rsa PrivateKey.Validate(), which is cubic-time on Go 1.24+. One crafted key, for example in an embedded jwk header passed to ParseSigned, burns CPU. Fixed in go-jose/v4 v4.1.6. v3 (β€3.0.5) has no patched version. Go 1.27.4/1.26.11 still aren't pre-announced, though #82536 (the ML-DSA ClientHello fix) is now cherry-pick approved.
go get golang.org/x/net@v0.62.0 in anything that parses or re-renders untrusted HTML, such as sanitizers, scrapers and email/HTML previewers. go-jose sits under many OIDC/JWT stacks. Check go mod why github.com/go-jose/go-jose/v3 in particular: v3 has no fix, so the only remedy is moving to v4.1.6.