CVE-2026-66392
Last modified
CVE-2026-66392 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. 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. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache bRPC | < 1.18.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-66392?
How severe is CVE-2026-66392?
How do I fix CVE-2026-66392?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-66381A repository reader with cache-deploy permission may access …5.3
- CVE-2026-66382An authenticated user may write files outside the intended A…4.3
- CVE-2026-66384An authenticated user may write data outside the intended Do…5.3
- CVE-2026-6639The AI Chatbot & Workflow Automation by AIWU plugin for Word…7.5
- CVE-2026-66390Improper Neutralization of Input During Web Page Generation …6.1
- CVE-2026-66391Use of Insufficiently Random Values, Protection Mechanism Fa…6.5
- CVE-2026-66393NLTK versions before 3.9.4 contain an unbounded recursion vu…7.5
- CVE-2026-66394SiYuan before v3.7.3 contains stored and reflected cross-sit…8.7
- CVE-2026-66395SiYuan desktop before v3.7.2 contains a reflected cross-site…9.6
- CVE-2026-66396SiYuan before v3.7.2 fails to escape the title-img Individua…8.4
- CVE-2026-66397phpMyFAQ before 4.1.6 fails to validate path traversal seque…8.6
- CVE-2026-66398phpMyFAQ before v4.1.6 contains a remote code execution vuln…9.4
Are you affected by CVE-2026-66392?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
