The Post-Quantum REALITY Split

Home › Guides › The Post-Quantum REALITY Split

✓ checked 15 October 2026 · sources: GitHub commits, issues, releases and source code; IETF Datatracker · method · caveats · download the data

Since 8 September 2026, servers running new versions of Xray-core’s REALITY protocol have refused REALITY clients whose TLS ClientHello lacks a post-quantum X25519MLKEM768 key share, and sing-box’s REALITY client removes that key share. The result, reported in sing-box issue #4520, is that sing-box clients fail to connect to those servers with “reality verification failed”. All 4 Xray-core releases since then include the change; sing-box 1.14.3, released on 9 October, still removes the key share. The issue has been open for 34 days.

Read this first. Xray-core, sing-box and mihomo are open-source proxy tools. Many people use them to get around network censorship, and they’re also used for ordinary proxying. This page is a dated record of what the code, commits and issue reports show. It doesn’t judge either project’s choices, and the issue comments we cite are from users, not maintainers, unless we say so.

Xray-core releases requiring the key share 4sing-box issue #4520 open since 11 Sep 2026X25519MLKEM768 code point 4588

Headline findings

  1. The rule is in one REALITY commit. Commit 8cdf7bf in XTLS/REALITY, dated 8 September 2026, is titled “REALITY protocol: Reject outdated/strange Client Hello that doesn’t have X25519MLKEM768 before optional X25519”. The code stops treating a ClientHello as a REALITY client unless an X25519MLKEM768 key share comes before any plain X25519 share. According to the #4520 report, the server then “silently falls back to the configured destination” (the real website a REALITY server imitates), so the client sees a verification failure rather than an error message.
  2. Every Xray-core release since then includes it. The go.mod files of v26.9.8, v26.9.9, v26.9.30 and v26.10.10 all pin REALITY version v0.0.0-20260908062103-8cdf7bf9c7f0. The last release before it, v26.7.28, pins an older version. A day earlier, maintainer RPRX wrote in Xray-core issue #6714 that the next version would make this the server default (the comment is in Chinese).
  3. sing-box’s code strips the key share. In sing-box 1.14.3 and 1.15.0-alpha.12, common/tls/reality_client.go filters X25519MLKEM768 out of both the supported_groups and key_share extensions before sending the ClientHello. The filter arrived in the commit “Update utls to v1.7.2”, written in May 2025 and merged in July 2025. A commenter in #4520 identified it on 14 October 2026 and posted a fix branch on a personal fork; it hadn’t been merged when we checked.
  4. mihomo makes the key share opt-in. mihomo’s current REALITY client removes X25519MLKEM768 unless the outbound sets support-x25519mlkem768; its code comment says the key share “does not work properly with the old reality server”. A mihomo pull request that set out to “synchronize REALITY with Xray ML-KEM” was closed without being merged.
  5. The tools are widely used. On GitHub, Xray-core has 42,116 stars, sing-box 38,896 and mihomo 34,900. The GUI clients v2rayN (118,278) and Hiddify (33,216) list both Xray and sing-box in their repository descriptions.

Timeline

Dates are UTC, from GitHub and the IETF Datatracker.

DateProjectEvent
7 September 2026Xray-coreAn Xray maintainer (RPRX) says in issue #6714 that the next version will change the REALITY server default · source
8 September 2026REALITYCommit 8cdf7bf: “REALITY protocol: Reject outdated/strange Client Hello that doesn’t have X25519MLKEM768 before optional X25519” · source
8 September 2026Xray-corev26.9.8 released, the first release whose go.mod pins REALITY 8cdf7bf · source
8 September 2026Xray-corev26.9.9 released (same REALITY version) · source
11 September 2026sing-boxIssue #4520 opened, reporting “reality verification failed” against Xray-core v26.9.8+ servers · source
15 September 2026sing-boxv1.14.1 released; reported in #4520 as still failing · source
24 September 2026sing-boxv1.14.2 released · source
30 September 2026Xray-corev26.9.30 released (same REALITY version) · source
9 October 2026sing-boxv1.14.3 released; its reality_client.go still removes X25519MLKEM768 · source
10 October 2026Xray-corev26.10.10 released (same REALITY version) · source
12 October 2026IETFdraft-ietf-tls-mlkem revision 11 posted · source
14 October 2026sing-boxA commenter in #4520 traces the failure to a filter in sing-box’s own REALITY client · source
14 October 2026sing-boxThe same commenter posts a fix branch on a personal fork; the issue stays open · source

What each version’s code does

ProjectVersionReleasedWhat we found
Xray-corev26.7.2828 July 2026older REALITY (before 8cdf7bf)
Xray-corev26.9.88 September 2026requires X25519MLKEM768 key share
Xray-corev26.9.98 September 2026requires X25519MLKEM768 key share
Xray-corev26.9.3030 September 2026requires X25519MLKEM768 key share
Xray-corev26.10.1010 October 2026requires X25519MLKEM768 key share
sing-boxv1.14.39 October 2026removes X25519MLKEM768 from supported_groups and key_share
sing-boxv1.15.0-alpha.1211 October 2026removes X25519MLKEM768 from supported_groups and key_share
mihomoMeta branch (checked 15 Oct 2026)–removes X25519MLKEM768 unless the support-x25519mlkem768 option is set

The issue reporter tested sing-box 1.12.25, 1.14.0, 1.14.1 and 1.15.0 alphas against Xray-core v26.9.9 and reported that all of them failed, while an Xray-core client with the same settings connected. Another commenter reported that rolling the server back to Xray-core 26.6.27 restored sing-box connections. We haven’t reproduced these tests.

What X25519MLKEM768 is

X25519MLKEM768 is a hybrid key exchange for TLS 1.3. It combines the classic X25519 exchange with ML-KEM-768, the post-quantum algorithm NIST standardised in FIPS 203. The IETF draft draft-ietf-tls-ecdhe-mlkem (revision 05) gives it code point 4588 (0x11EC), with the comment “Combining X25519 ECDH with ML-KEM-768”. A separate draft for ML-KEM on its own, draft-ietf-tls-mlkem, reached revision 11 on 12 October 2026. A commenter in #4520 says Chrome has sent this key share since version 131. The #4520 report used sing-box’s chrome uTLS fingerprint, which is meant to make the ClientHello look like Chrome’s.

Projects on GitHub

RepositoryStars, 15 Oct 2026Licence (GitHub)
2dust/v2rayN118,278GPL-3.0
2dust/v2rayNG64,022GPL-3.0
XTLS/Xray-core42,116MPL-2.0
SagerNet/sing-box38,896not detected
MetaCubeX/mihomo34,900MIT
hiddify/hiddify-app33,216not detected
XTLS/REALITY5,543MPL-2.0

Method

On 15 October 2026 we pulled the REALITY commit, the Xray-core and sing-box release lists, sing-box issue #4520 and its comments, the linked Xray-core comment, mihomo pull request #2983 and repository metadata from the GitHub REST API. To see which Xray-core releases contain the change, we read the go.mod file at each release tag. To see what sing-box sends, we read common/tls/reality_client.go at the v1.14.3 and v1.15.0-alpha.12 tags, and mihomo’s REALITY client on its Meta branch. Draft revisions come from the IETF Datatracker API. A separate script rechecks every date, version, count and quote against the saved files.

Caveats

  • We read source code; we didn’t run connection tests. Behaviour can also depend on configuration, client fingerprint settings and server options.
  • Comments in issue #4520 come from users and contributors, not sing-box maintainers. sing-box maintainers hadn’t posted in the issue when we checked.
  • Xray-core marks all its GitHub releases as pre-releases, so “release” here means a tagged GitHub release.
  • Star counts measure GitHub attention, not the number of users.

Download the data

  • Timeline (CSV): every dated event above, with its source URL.
  • Code checks (CSV): what each checked version pins or does, with links to the file.

Cite as: ProxyPicker, “The Post-Quantum REALITY Split”, 15 October 2026, https://proxypicker.com/post-quantum-reality-split/. Sources: GitHub, IETF Datatracker.

Related: Tor exit relays and Russian bridge users · MASQUE tracker · Privacy Pass tracker.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.