For your digest
github.com/xtls/xray-core: Xray-core: Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
github.com/xtls/xray-core (Go)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- github.com/xtls/xray-core (Go): from 1.260113.0, before 1.260327.1-0.20260710210335-64fada32b5b9
- github.com/xtls/xray-core (Go): from 1.260113.0, before 1.260327.1-0.20260710210335-64fada32b5b9
The fix
github.com/xtls/xray-core (Go) fixed in 1.260327.1-0.20260710210335-64fada32b5b9
gogo get github.com/xtls/xray-core@v1.260327.1-0.20260710210335-64fada32b5b9Check what is installedgo list -m github.com/xtls/xray-corePaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency github.com/xtls/xray-core to 1.260327.1-0.20260710210335-64fada32b5b9 or the nearest later release, to fix GHSA-5wf9-h793-w73c. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".