github lilendian0x00/xray-knife v11.5.1
Xray-knife v11.5.1

one hour ago

🚀 Xray-knife v11.5.1 (JOIN THE TELEGRAM CHANNEL)

https://t.me/lilendian0x00

xray-core moves to 26.11.9. Upstream withdrew 26.10.29, the version v11.5.0 shipped. 🛠️

⚠️ After upgrading

  • 🧰 Go 1.27.4 is needed to build from source.

🔓 Plaintext links follow xray-core's private rule

xray-core only lets VLESS and Trojan go without TLS to 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fc00::/7, loopback and link-local addresses, or a private domain. v11.5.0 checked a wider list, so a plaintext link to CGNAT (100.64.0.0/10), 198.18.0.0/15, 6to4, Teredo or NAT64 stayed on xray-core, which then refused it. With -z auto those links now run on sing-box whenever it has the transport, like any other public server.

That also corrects the v11.5.0 note: for this check, 6to4, Teredo and NAT64 count as public.


🆙 xray-core 26.11.9

  • 🚫 Upstream withdrew 26.10.29 (and 26.10.10, 26.10.17) because their built-in root CAs had broken keys.
  • 🛡️ MPTCP is off on listeners (CVE-2026-98432, a Linux kernel use-after-free). Go listens with MPTCP by default, so xray-knife's own listeners (proxy inbounds, the web UI) turn it off too.
  • 🌐 Plain fp=chrome now sends Chrome 155, and fp=hellochrome_155 works.

📦 Install

Grab a prebuilt binary from the assets below (verify with sha256sum -c --ignore-missing SHA256SUMS), or install with Go. The tags match the release binaries:

go install -tags "with_gvisor,with_quic,with_wireguard,with_utls,with_clash_api,with_grpc" \
  github.com/lilendian0x00/xray-knife/v11@latest

Full Changelog: v11.5.0...v11.5.1

Don't miss a new xray-knife release

NewReleases is sending notifications on new releases.