CVE-2025-65083: GoSign Desktop through 2.4.1 disables TLS certificate validation when configured to use a proxy server
Source GCVE Database
Not known to be exploited · CVSS 3.2 Low.
Data as of 13 Nov 2026, 19:35 UTC
Thin evidence
One scorer or none| CNA (mitre) | CVSS 3.1 | 3.2 |
|---|
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 13 Nov 2026.
What to do
AI-suggested
Users should avoid configuring GoSign Desktop to use arbitrary or untrusted proxy servers. Ensure that proxy servers enforce strict TLS certificate validation. Additionally, avoid placing the ~/.gosign directory in the home directory of untrusted users to prevent execution of potentially malicious downloaded files. Monitor vendor advisories for any future updates or patches addressing this issue.
Description
GoSign Desktop versions through 2.4.1 disable TLS certificate validation when configured to use a proxy server. This behavior can allow bypassing integrity protection if a user selects an arbitrary proxy server that accepts untrusted or invalid server certificates. The vulnerability is limited by typical enterprise proxy configurations that do not permit such insecure connections. The issue is classified as low severity with a CVSS score of 3.2.