Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-105218Published 2026-10-04

CVE-2026-105218 — go-pay gopay

high

As of 2026-10-05, CVE-2026-105218 is a HIGH-severity vulnerability in go-pay gopay, CVSS v3.1 7.4, EPSS 0.1% (5.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-105218 as of 2026-10-05; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.4/10High
EPSS
0.1%Higher than 5.0% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.9/10Threadlinqs triage score
Published
Updated 2026-10-05
CVSS v3.1 7.4 (HIGH) · CVSS v4.0 9.1 · EPSS 0.1% (higher than 5.0% of all scored CVEs) · Priority 3.9/10 · Published 2026-10-04

Last updated:

What is 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.

The record classifies CVE-2026-105218 under weakness class CWE-295. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 46 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.4 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0 base score
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
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 5.0% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-04

Is CVE-2026-105218 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

Affected products and versions

  • go-pay: gopay

How to fix CVE-2026-105218

Patch reference: https://github.com/go-pay/gopay/commit/f6df04fd4f64a2ad2c303ba063b6502bfdd259fd. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-105218

No threat campaign in the Threadlinqs corpus currently references CVE-2026-105218, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, GitHub Security Advisories, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Technical analysis

Third-party advisory

Issue tracking and product pages