CVE-2026-66392

{"id": "CVE-2026-66392", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-66392", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-10-30T17:54:43.784196Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.2}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"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"}]}], "published": "2026-10-21T12:17:22.417", "references": [{"url": "https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb", "source": "security@apache.org"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-297"}]}], "descriptions": [{"lang": "en", "value": "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.\n\n\nAffected Scenarios:\nApplications 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.\n\n\nHow to Fix:\nUpgrade 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 .\n\nNote:\nThe 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."}, {"lang": "es", "value": "Versiones de Apache bRPC anteriores a 1.18.0 validan la cadena de certificados del servidor cuando la verificaci\u00f3n de pares TLS del cliente est\u00e1 habilitada, pero no vinculan el certificado a un nombre DNS o direcci\u00f3n IP esperado. Un atacante de red que pueda redirigir o interceptar una conexi\u00f3n y que posea un certificado emitido por una CA de confianza del cliente para otro nombre puede suplantar el endpoint TLS solicitado.\\n\\nEscenarios afectados:\\nLas aplicaciones usan un Canal cliente bRPC para conectarse a una red no confiable con la verificaci\u00f3n de certificado habilitada y conf\u00edan en una CA que puede emitir certificados para identidades distintas del endpoint previsto.\\n\\nC\u00f3mo corregir:\\nActualice a Apache bRPC 1.18.0 y habilite VERIFY_PEER con un verify_depth positivo. Los canales HTTPS verifican autom\u00e1ticamente el certificado contra el host en la URL del Canal. Los llamadores pueden establecer VerifyOptions::expected_peer_name expl\u00edcitamente cuando la identidad del certificado difiere del host de la URL. Alternativamente, aplique el parche de https://github.com/apache/brpc/pull/3408.\\n\\nNota:\\nLa nueva opci\u00f3n realiza la verificaci\u00f3n de DNS SAN o IP SAN durante el apret\u00f3n de manos TLS. Las configuraciones que establecen expected_peer_name mientras la verificaci\u00f3n de pares est\u00e1 deshabilitada son rechazadas."}], "lastModified": "2026-10-30T18:18:03.973", "sourceIdentifier": "security@apache.org"}