Apache bRPC: TLS Client Accepts Certificates for Mismatched Peer Names
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.
CVE-2026-66392
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-66392
Apache bRPC
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Apache Software Foundation",
"product": "Apache bRPC",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "1.18.0",
"versionType": "semver"
}
],
"packageURL": "pkg:github/apache/brpc",
"packageName": "apache/brpc",
"collectionURL": "https://github.com",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-66392
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #45856 · Revision 1
- Added to Heist Feed
- Publisher date