- CVE-2026-48618: normalize the peer hostname with domainToASCII() before splitting it into DNS labels in tls.checkServerIdentity(), so the verifier counts the same labels the resolver connected to; Unicode dot separators (U+3002, U+FF0E, U+FF61) can no longer defeat the wildcard-depth rule and make a *.example.com certificate authenticate a host two levels below it (backport of nodejs/node 1efb4ff51a plus the required IPv6 IP-SAN follow-up 1d87a24050) - CVE-2026-48928: add the 'i' flag to the SNI RegExp built by tls.Server.prototype.addContext(), so an uppercase or mixed-case SNI hostname selects its per-hostname SecureContext instead of silently falling back to the server's default context and bypassing per-tenant client-certificate authorization in multi-context mTLS deployments (backport of nodejs/node 39d1d09684) - CVE-2026-48934: bind a reusable TLS client session to the host it was authenticated for, so a session obtained from host A can no longer be replayed against host B to skip checkServerIdentity() via isSessionReused(); adds wrapSessionState/getSessionForReuse and an explicit TLSSocket.prototype.getSession (backport of nodejs/node fd890ba01d, with the fix's optional chaining rewritten to && form because V8 7.8 has no ?.) - CVE-2026-58040: bind identity checks to session and socket reuse in the https.Agent, the vector CVE-2026-48934 left open. A request supplying its own checkServerIdentity is tagged with a unique per-request index that Agent.prototype.getName() appends, so it gets its own pool bucket; createConnection() neither reads nor writes the TLS session cache for it, and a new keepSocketAlive() override keeps its socket out of freeSockets. A later request using the default strict check can therefore no longer inherit a session or a keep-alive socket authenticated under permissive rules and be reported authorized against an unverified host (backport of nodejs/node 51123159fe)