{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105218 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105218 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105218 is a critical vulnerability in go-pay gopay, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-105218 and fix it if it is affected.\n\nWhat it is: CVE-2026-105218 is a critical vulnerability in go-pay gopay, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-105218 in the wild and no public exploit code.\n\nAffected product: go-pay gopay. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105218/ (Markdown: https://insights.sbomify.com/CVE-2026-105218/index.md)","id":"CVE-2026-105218","markdown":"https://insights.sbomify.com/CVE-2026-105218/index.md","name":"CVE-2026-105218","record":{"aliases":["GHSA-8f6w-7m2h-mfwg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Go payment library","requires_auth":"none","summary":"Man-in-the-middle attackers can intercept and modify payment data due to disabled TLS certificate verification in the xhttp client.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"gopay before 1.5.119 Disabled TLS Certificate Verification in xhttp Client","id":"CVE-2026-105218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Mammoth.js 1.3.0 before 1.12.3 ReDoS via Style Map Tokeniser","id":"CVE-2026-105219"},"packages":[],"prev":{"headline":"Cockpit CMS 2.12.0 before 2.14.1 Disabled TLS Verification via cron.php","id":"CVE-2026-105217"},"products":["gopay"],"published":"2026-10-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["go-pay"]},"summary":"Man-in-the-middle attackers can intercept and modify payment data due to disabled TLS certificate verification in the xhttp client.","url":"https://insights.sbomify.com/CVE-2026-105218/"}