# Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks in github.com/xtls/xray-core Advisory record · `GHSA-5wf9-h793-w73c` - **Identifiers:** `GHSA-5wf9-h793-w73c` · `GO-2026-6651` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **Published:** 20 Oct 2026 - **Updated:** 5 Nov 2026 - **Reviewed by a person:** No 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. ## Affected packages - `github.com/xtls/xray-core` (Go): affected `>=1.260113.0, <1.260327.1-0.20260710210335-64fada32b5b9`; fixed in `1.260327.1-0.20260710210335-64fada32b5b9` ## 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 - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5wf9-h793-w73c) ## Sources - [GitHub Advisory Database: GHSA-5wf9-h793-w73c](https://github.com/advisories/GHSA-5wf9-h793-w73c) - [OSV: GHSA-5wf9-h793-w73c](https://osv.dev/vulnerability/GHSA-5wf9-h793-w73c) - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .