CVE-2026-105218

gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client

Published Oct 4, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability disables TLS certificate verification in the default HTTP client used by the gopay library. This allows an attacker to act as a man‑in‑the‑middle, presenting any certificate and thereby intercepting merchant credentials, transaction signatures, and other sensitive data. The attacker can also alter payment, refund and order query responses, creating fraudulent transactions or disabling legitimate ones.

Affected Systems

Any application that incorporates the go-pay library version before 1.5.119 is affected. The exposed component is the gopay/xhttp client, which is used in merchant payment integrations to communicate with payment provider APIs.

Risk and Exploitability

The CVSS score is 9.1, indicating a high severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The risk is significant because the flaw provides a remote attacker with the ability to interpose and modify traffic over TLS. Exploitation requires the attacker to intercept traffic between the merchant infrastructure and the payment provider, which is feasible in compromised network environments or through DNS hijacking. The vulnerability does not require privileged access and can be abused by attackers with network visibility or control. Due to its severity and the ease of exploitation when certificate checks are disabled, immediate mitigation is recommended.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the gopay library to version 1.5.119 or later.
  • Verify that your application does not override TLS verification settings such as InsecureSkipVerify in the HTTP client.
  • If an upgrade is not immediately possible, implement stricter TLS validation by using a custom client that enforces certificate checks and reject any self‑signed or untrusted certificates.

Generated by OpenCVE AI on October 4, 2026 at 18:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Go-pay
Go-pay gopay
Vendors & Products Go-pay
Go-pay gopay
Type Values Removed Values Added
Description 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.
Title gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.1, 'vector': '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'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 5, 2026, 2:55 PM
Reserved
Oct 4, 2026, 1:04 PM
Status
Deferred
Published
Oct 4, 2026, 6:16 PM
Modified
Oct 6, 2026, 4:08 PM