Vulnerability in Go-Pay Gopay
CVE-2026-105218
gopay before 1.5.119 disables TLS certificate verification in defaultClient() in pkg/xhttp/client.go, allowing man-in-the-middle attackers to impersonate payment provider APIs. Attackers can present any certificate to read merchant credentials, signatures and transaction data, and modify payment, refund and order query responses.
Vulnerability class: Improper Certificate Validation
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/go-pay/gopay/issues/540 (issue-tracking)
- github.com/go-pay/gopay/commit/f6df04fd4f64a2ad2c303ba063b6502bfdd259fd (patch)
- github.com/go-pay/gopay/blob/v1.5.118/pkg/xhttp/client.go (technical-description)
- github.com/go-pay/gopay (product)
- www.vulncheck.com/advisories/gopay-before-1.5.119-disabled-tls-certificate-veri… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-105218?
- CVE-2026-105218 is a high-severity vulnerability in Go-Pay Gopay, classified under Improper Certificate Validation. CVSS score: 7.4/10. Published 2026-10-04.
- How severe is CVE-2026-105218?
- High severity. CVSS v3 base score is 7.4 out of 10.