CVE-2026-105218 json
gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client
published 2026-10-04 35 d ago modified 2026-10-06 33 d ago also EUVD-2026-92121
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 34 d ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- go-pay gopay
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
github.com
/go-pay/gopay/commit/f6df04fd4f64a2ad2c303ba063b6502bfdd259fd
patch
-
github.com
/go-pay/gopay/issues/540
issue-tracking
-
github.com
/go-pay/gopay/blob/v1.5.118/pkg/xhttp/client.go#L15-L37
technical-description
-
github.com
/go-pay/gopay
product
-
vulncheck.com
/advisories/gopay-before-1.5.119-disabled-tls-certificate-verification-in-xhttp-client
third-party-advisory
Sources
- CVE List CVE-2026-105218
- NVD CVE-2026-105218
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.