Skip to content- Sources: primary, discussion, further discussion
- Summary: GHSA-5wf9-h793-w73c, published 2026-07-10, records that setting
pinnedPeerCertSha256 in Xray-core turns off the standard certificate verification rather than adding to it, so hostname checking was skipped whenever ServerName ended up empty. The advisory's title and vulnerable branch scope the machine-in-the-middle condition to a pinned well-known, non-self-signed CA certificate: when the pinned hash matches a CA rather than the presented leaf, any leaf issued under that CA satisfies the check. Pinning a leaf certificate's own hash is not in that scope, because the presented leaf is then matched directly. The advisory states that Xray-core usually derives ServerName from the server address, and names the two paths where it does not and so leaves neither dNSName nor iPAddress checked: the Hysteria2 dialer, and gRPC dial when the address is an IP address rather than a domain. It lists affected versions from v26.1.13 and patched versions from v26.7.11, rates the severity Low, and records no known CVE, and the net4people thread holds that the first code change addressing the flaw shipped without a security note, which was not verified against the commit and release history here. - Why it matters: Pinning a shared CA's hash through
pinnedPeerCertSha256 is weaker than ordinary verification on those two dial paths, because every leaf that CA issues then passes.