CVE-2026-66392
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-297 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-3522 | Medium | 4.0 | 5.6% | - | Fix |
| CVE-2018-10936 | High | 8.1 | 2.9% | - | Fix |
| CVE-2020-1887 | Critical | 9.1 | 1.6% | - | Fix |
| CVE-2024-2466 | Medium | 6.5 | 1.5% | - | Fix |
| CVE-2020-14387 | High | 7.4 | 1.1% | - | Fix |
| CVE-2020-15260 | Medium | 6.8 | 1.0% | - | Fix |
Common questions
How do I fix CVE-2026-66392?
No published fix for CVE-2026-66392 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-66392 being actively exploited?
Not that we know of. CVE-2026-66392 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.10% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-66392?
CVE-2026-66392 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-66392
Markdown
[](https://tridentstack.com/cve/CVE-2026-66392)HTML
<a href="https://tridentstack.com/cve/CVE-2026-66392"><img src="https://tridentstack.com/cve/badge/CVE-2026-66392.svg" alt="CVE-2026-66392"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-30.