- Exploited
- No known exploitation
- Fix
- Fixed in 1.260327.1-0.20260710210335-64fada32b5b9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.260327.1-0.20260710210335-64fada32b5b9.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks in github.com/xtls/xray-core
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Go packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.260327.1-0.20260710210335-64fada32b5b9.
Timeline
- Advisory published16 days
- Record last updated
Affected versions
From 1.260113.0 · fixed in 1.260327.1-0.20260710210335-64fada32b5b9
Evidence 4
- Advisory
- Patch
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about GO-2026-6651
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: cve.now feed data
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: cve.now feed data
How do I fix GO-2026-6651?
Upgrade to a fixed version: 1.260327.1-0.20260710210335-64fada32b5b9.Source: cve.now feed data