gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-295.
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA gopay (go-pay) Fixed in 1.5.119
Timeline
- 2026-10-04 Threatist record created from CVE-2026-105218
- 2026-10-04 Alias added: GHSA-8f6w-7m2h-mfwg
- 2026-10-05 CISA SSVC decision points changed
- 2026-10-05 Priority changed: MEDIUM → LOW
- 2026-10-05 Priority changed: LOW → MEDIUM
References
Sources
- CVE-2026-105218 · CVE Program
- CVE-2026-105218 · NVD
- FIRST EPSS
- GHSA-8f6w-7m2h-mfwg · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences