CVE-2026-75595
Netty: SNI routing bypass with a fragmented TLS ClientHello
| Published | 2026-08-19 |
|---|---|
| Last updated | 2026-11-16 |
| Component | Netty (shaded in the Qdrant gRPC client transport) |
| Severity | High |
| PageSeeder status | Not affected |
Summary
A fragmented TLS ClientHello can cause an affected Netty server to select its default TLS context instead of the context configured for the requested server name. If client certificates are required only by the server name specific context, the default context permits connections without certificates, and the application performs no separate certificate check, this can bypass mutual TLS.
PageSeeder 6.3000–6.3004 include Netty 4.1.124.Final within the shaded Qdrant gRPC client, which falls within the upstream affected version range. PageSeeder uses this transport for outbound connections; its standard Qdrant integration does not create the Netty TLS server or SNI configuration required to trigger the vulnerability. The assessed standard configuration is therefore not affected.
The upstream advisory rates the issue High and identifies Netty 4.1.137.Final and 4.2.17.Final as fixed versions. The CVE record assigns a CVSS 4.0 score of 9.1 (Critical). These ratings describe the vulnerable server configuration, not PageSeeder’s assessed exposure.
PageSeeder impact assessment
| Affected dependency | io.grpc:grpc-netty-shaded 1.75.0 (contains Netty 4.1.124.Final); io.qdrant:client 1.18.1 |
|---|---|
| PageSeeder versions assessed | PageSeeder 6.3000–6.3003: Qdrant construction and embedding enablement checked. Current 6.3004 source and cached transport: integration and shaded code checked. |
| Vulnerability status | Not affected |
| Conditions required for exploitation | Netty TLS server with SNI-specific SSL contexts and permissive default context. PageSeeder uses Netty as an outbound client only. |
| Relevant PageSeeder configuration | Qdrant was introduced in PageSeeder 6.3000 and is used only when AI embedding is enabled and a Qdrant store is configured. The store defaults to localhost:6334 with TLS disabled. Qdrant is expected to be maintained within a private network. The client builder accepts a configured host, port, TLS flag, API key and optional timeout; it does not create a Netty TLS listener or install an SNI handler. |
| Assessment date | 2026-11-16 |
Assessment
PageSeeder 6.3000–6.3003 use the Qdrant client as an outbound gRPC connection only when AI embedding is enabled and configured.
This vulnerability affects Netty TLS servers with specific SNI and mutual-TLS configurations. PageSeeder's Qdrant integration operates as a client and does not create a Netty TLS listener or install SNI handlers, so the vulnerable code path cannot be triggered.
Recommended action
No action required
PageSeeder is not affected by this vulnerability in its default Qdrant client configuration.
Continue to maintain Qdrant on a private network and enable AI embedding only where needed. Reassess if your deployment adds custom Netty TLS servers, SNI handlers, or modified gRPC transports.