Advisory severityUnratedApache Software Foundation Updated

Advisory [CVE-2026-66392] 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

This security Apache Software Foundation advisory covers CVE-2026-66392; related products: Apache bRPC.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-66392 Source published Oct 21, 2026Source updated Oct 21, 2026

VulniPulse record published Oct 21, 2026Record updated Oct 21, 2026

CVE-2026-66392

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

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.

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.

Affected versions

Apache bRPC before 1.18.0

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

1.18.0

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation

How to Fix: Upgrade to Apache bRPC 1.18.0 and enable VERIFY_PEER with a positive verify_depth.
Alternatively, apply the patch from https://github.com/apache/brpc/pull/3408.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Sources

Official and corroborating records used to build this advisory.

Official vendor advisoryofficial
Official advisory page fetched and parsed; accepted detail fields are attributed to this page.
Apache Software Foundation
CVE.org CNA recordCVE.org
Independent CNA record used for near-real-time discovery and missed-CVE reconciliation. Discovered from the machine-readable feed https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/delta.json; this link opens the CVE.org record for CVE-2026-66392 instead of the raw feed document.
CVE Program

Cross-references

Validate CVE metadata against the authoritative registries.

CVE-2026-66392NVD CVE.org MITRE

Official resources

ASF Security — reporting & CVE process
Official documentation
The Apache Software Foundation's official security page: how ASF CVEs are published and where each project's advisories live.
Apache project downloads (fixed releases)
Official documentation
Official ASF download tree — fetch the fixed release named in this advisory from the project's directory.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.