Live › vulnerability › CVE-2026-66392
Go to dashboardApache bRPC before 1.18.0 checks the certificate chain on client TLS connections but does not check that the certificate names the host being connected to. A network attacker holding a certificate from a CA the client trusts can impersonate the target endpoint.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use a bRPC client Channel over TLS with certificate verification enabled, connecting across an untrusted network, and that trust a CA able to issue certificates for other names. Services that only talk to bRPC on a trusted private network, or that do not use TLS client channels, are less exposed. HTTPS Channels verify the certificate against the URL host automatically once upgraded.
No product ranges from the sources yet.
grep -ri brpc in the project's dependency manifests or lockfiles and check the bRPC version in use1.18.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Apache bRPC versions before 1.18.0 validate the server certificate chain when client TLS peer verification is enabled, but do not bind the certificate to an expected DNS name or IP address. A network attacker who can redirect or intercept a connection and who possesses a certificate issued by a CA trusted by the client for another name may impersonate the requested TLS endpoint.
Affected Scenarios: Applications use a bRPC client Channel to connect to an untrusted network with certificate verification enabled and trust a CA that can issue certificates for identities other than the intended endpoint.
How to Fix: Upgrade to Apache bRPC 1.18.0 and enable VERIFY_PEER with a positive verify_depth. HTTPS Channels automatically verify the certificate against the host in the Channel URL. Callers may set VerifyOptions::expected_peer_name explicitly when the certificate identity differs from the URL host. Alternatively, apply the patch from https://github.com/apache/brpc/pull/3408 .
Note: The new option performs DNS SAN or IP SAN verification during the TLS handshake. Configurations that set expected_peer_name while peer verification is disabled are rejected.
This page as .md · .json · in your agent: get_signal("CVE-2026-66392")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.