Duplicate Advisory: TLS certificate validation error in mellium.im/xmppGHSA-m658-p24x-p74r
MEDIUMFix: mellium/xmpp#260GHSA-m658-p24x-p74r is a medium-severity (CVSS 5.9) CWE-295 vulnerability in mellium.im/xmpp. A fix is available for mellium.im/xmpp — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-m658-p24x-p74r by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
mellium.im/xmppReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-h289-x5wc-xcv8. This link is maintained to preserve external references.
Original Description
In Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | mellium.im/xmpp | ≥ 0.18.0&&< 0.21.1 | 0.21.1go get mellium.im/xmpp@v0.21.1 |
Affected Products
xmppmelliumDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mellium.im/xmpp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mellium.im/xmpp to 0.21.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m658-p24x-p74r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-m658-p24x-p74r in your dependencies?
Find it across Go, including transitive dependencies.