* SECURITY UPDATE: TLS wildcard-depth authentication bypass via Unicode dot separators - debian/patches/CVE-2026-48618.patch: 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; U+3002, U+FF0E and U+FF61 can no longer defeat the wildcard-depth rule in check() and make a certificate for *.example.com authenticate a host two levels below it. Includes the required IPv6 IP-Address-SAN follow-up so IPv6 literals keep matching their IP SANs (backport of nodejs/node 1efb4ff51a and 1d87a24050) - CVE-2026-48618 * SECURITY UPDATE: uppercase SNI mTLS authorization bypass - debian/patches/CVE-2026-48928.patch: add the 'i' flag to the RegExp built by tls.Server.prototype.addContext(), so an uppercase or mixed-case SNI hostname selects its per-hostname SecureContext as RFC 6066 Section 3 requires 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-48928 * SECURITY UPDATE: TLS session replay skips host identity verification - debian/patches/CVE-2026-48934.patch: 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() through isSessionReused(); adds wrapSessionState()/getSessionForReuse() and an explicit TLSSocket.prototype.getSession(). The fix's optional chaining is rewritten to && form because Node 12's V8 7.8 has no ?. (backport of nodejs/node fd890ba01d) - CVE-2026-48934 * SECURITY UPDATE: https.Agent reuses connections authenticated under a different identity check - debian/patches/CVE-2026-58040.patch: 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, which Agent.prototype.getName() now 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 that was authenticated under permissive rules and be reported authorized against an unverified host (backport of nodejs/node 51123159fe) - CVE-2026-58040