Skip to main content
VulnerabilityPublished

CVE-2026-105218: go-pay gopay · Improper Certificate Validation

Affects go-pay gopaySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.5.119 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.5.119
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade gopay and github.com/go-pay/gopay to 1.5.119.

Affected software

ProductAffectedFixed in
go-paygopayAffected
  • <1.5.119
Fixed in
  • 1.5.119
Gogithub.com/go-pay/gopaypkg:golang/github.com/go-pay/gopayOther threatsAffected
  • <1.5.119
Fixed in
  • 1.5.119

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in gopay version 1.5.119 and later. Users should upgrade to version 1.5.119 or newer to ensure TLS certificate verification is properly enforced. Until upgrading, users should avoid using vulnerable versions to prevent man-in-the-middle attacks. Patch status is confirmed by the affectedVersions data indicating versions before 1.5.119 are vulnerable.

Description

A critical vulnerability (CVE-2026-105218) exists in gopay versions before 1.5.119 where TLS certificate verification is disabled in the defaultClient() function. This flaw allows man-in-the-middle attackers to impersonate payment provider APIs by presenting any certificate, enabling them to read sensitive merchant credentials, signatures, and transaction data, as well as modify payment, refund, and order query responses.

References

Community reviews

Loading reviews…