CVE-2026-105218

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-04. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 4, 2026

Last Modified

October 4, 2026

Advisory Details (5)

Auto-updated Oct 4, 2026
Patch available. Sources: github_commit.
generic

gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gopay-before-1.5.119-disabled-tls-certificate-verification-in-xhttp-client
generic

GitHub - go-pay/gopay: 微信、支付宝、抖音、通联支付、拉卡拉、PayPal、Apple 的Go版本SDK。【极简、易用的聚合支付SDK】 · GitHub

https://github.com/go-pay/gopay
generic

gopay/pkg/xhttp/client.go at v1.5.118 · go-pay/gopay · GitHub

https://github.com/go-pay/gopay/blob/v1.5.118/pkg/xhttp/client.go#L15-L37
github_commit Patch Available

commit f6df04fd4f64 (go-pay/gopay)

Patch available: go-pay/gopay v1.5.119 (contains commit f6df04fd4f64)

https://github.com/go-pay/gopay/commit/f6df04fd4f64a2ad2c303ba063b6502bfdd259fd
generic

CWE-295 + CWE-798: Global TLS verification disabled + hardcoded RSA private key in AllInPay cert · Issue #540 · go-pay/gopay · GitHub

https://github.com/go-pay/gopay/issues/540

Vendor Advisories for CVE-2026-105218(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 05:39 UTCEG score recompute
  2. 2026-10-05 05:39 UTCGHSA enrichment
  3. 2026-10-04 18:30 UTCEG score recompute
  4. 2026-10-04 17:18 UTCEG score recompute
  5. 2026-10-04 17:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-105218?
CVE-2026-105218 is a high vulnerability published on October 4, 2026. 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,…
When was CVE-2026-105218 disclosed?
CVE-2026-105218 was first published on October 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-105218?
CVE-2026-105218 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105218?
A fix for CVE-2026-105218 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105218 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-105218

Explore →

Is Your Infrastructure Affected by CVE-2026-105218?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs