Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-5wf9-h793-w73c

Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks in github.com/xtls/xray-core

No CVSS score

Published by the GitHub Advisory Database at 20 Oct 2026, 00:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/xtls/xray-coreGo>=1.260113.0, <1.260327.1-0.20260710210335-64fada32b5b91.260327.1-0.20260710210335-64fada32b5b9
Identifiers
GHSA-5wf9-h793-w73c · GO-2026-6651
Published
20 Oct 2026
Updated
5 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Xray-core versions from 1.260113.0 up to but not including 1.260327.1-0.20260710210335-64fada32b5b9 are affected. When a CA certificate is pinned via pinnedPeerCertSha256 and no server name is set, certificate hostname checks can be skipped in some transports (hysteria and grpc, where the server address is an IP address). An attacker who holds a certificate issued by the pinned CA for their own domain or IP address could intercept connections. Upgrade to 1.260327.1-0.20260710210335-64fada32b5b9 or later. The source gives no workaround beyond setting an explicit serverName.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.