CVE-2026-66392 Details
Description
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.
A vulnerability exists in Apache bRPC versions prior to 1.18.0, where the server certificate chain is validated during client TLS peer verification, but there is no binding of the certificate to an expected DNS name or IP address. This flaw allows a network attacker, who can redirect or intercept a connection and possesses a certificate from a trusted CA for a different name, to impersonate the desired TLS endpoint. The issue arises when applications use a bRPC client Channel to connect to an untrusted network with certificate verification enabled, trusting a CA that can issue certificates for identities other than the intended endpoint.
Users are advised to upgrade to Apache bRPC version 1.18.0 and enable peer verification with an appropriate verification depth. For HTTPS Channels, the certificate is automatically verified against the host in the Channel URL. If the certificate identity differs from the URL host, the expected peer name can be set explicitly. Alternatively, the patch available in Apache bRPC PR #3408 can be applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
VolerionCVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 21, 2026CISA-ADP
Assessed Oct 30, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb | [email protected] | AdvisoryBundleMailing ListRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-297 | Improper Validation of Certificate with Host Mismatch | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Apache bRPC | <= 1.17.0 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | CISA-ADP |
| Oct 26, 2026 | CVE Translated | [email protected] |
| Oct 21, 2026 | New CVE Received | [email protected] |