Read the docs

gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client

Priority MEDIUM 40CWE-295Published · Updated

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

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00163 5th percentileScored 2026-11-07
Fix Fixed gopay (go-pay): 1.5.119

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

VendorProductAffected versionsFixed inStatusSource
go-paygopaybefore 1.5.1191.5.119Patch availableCNA
  • gopay Vendorgo-pay Affected before 1.5.119 Fixed in 1.5.119 Patch available CNA

Remediation

  • Fix · CNA gopay (go-pay) Fixed in 1.5.119

Timeline

  1. 2026-10-04 Threatist record created from CVE-2026-105218
  2. 2026-10-04 Alias added: GHSA-8f6w-7m2h-mfwg
  3. 2026-10-05 CISA SSVC decision points changed
  4. 2026-10-05 Priority changed: MEDIUM → LOW
  5. 2026-10-05 Priority changed: LOW → MEDIUM

References

Sources