Xray-core hid a certificate bypass that left users exposed for half a year
Xray-core concealed a certificate verification bypass vulnerability
In January 2026, Xray-core replaced its pinnedPeerCertificateChainSha256 option with pinnedPeerCertSha256, which always skips regular certificate verification. A bypass in the new option let a man-in-the-middle insert a leaf certificate anywhere in the chain. The maintainers fixed it silently, never told users, and only a later incomplete fix forced a GitHub advisory. Users were left unprotected for nearly six months.
Xray-core itself is exactly the human factor that has left users insecure and "streaking".
- soltanov
Fixing the code is only half of incident response. Without an advisory, affected-version range, and downstream notification, users cannot know whether they remain exposed.
- usernomdeguerre
I get the impression that much of Xray's usage is in mainland China, do many other ecosystems use it? If not, why not?
Naively I would expect solutions out of Mainland China to be more sophisticated due to the internet restrictions within the country and the number of people who are digitally-connected.
But perhaps they cover for usecases one doesn't see outside the gfw.
- eriwang915
Xray-core's pinnedPeerCertSha256 treated an inserted leaf as the pinned cert, and the fix commit never called it a vulnerability.