CVE-2025-34324: Tinexta InfoCert S.p.A GoSign Desktop · Improper Verification of Cryptographic Signature
Affects Tinexta InfoCert S.p.A GoSign DesktopSource CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Tinexta InfoCert S.p.A. GoSign Desktop | Affected
| Fixed in– |
AI-suggested
Organizations should immediately audit their GoSign Desktop installations and update to a patched version once available. In the interim, enforce strict TLS certificate validation and disable any option that allows bypassing TLS checks, especially when proxies are in use. Implement network-level protections such as TLS interception detection and restrict proxy configuration changes to trusted administrators only. Digitally signing the update manifest should be prioritized by the vendor to ensure authenticity and integrity of updates. Organizations can also implement application whitelisting and endpoint detection and response (EDR) solutions to detect and block unauthorized code execution. Monitoring network traffic for unusual update requests and verifying update sources can help detect exploitation attempts. Additionally, educating users about the risks of proxy manipulation and ensuring least privilege principles on endpoints can reduce the impact of local attacks. Regular security assessments and penetration testing focusing on update mechanisms and proxy configurations are recommended to identify and remediate weaknesses.
Description
GoSign Desktop versions 2.4.0 and earlier use an unsigned update manifest for distributing application updates. The manifest contains package URLs and SHA-256 hashes but is not digitally signed, so its authenticity relies solely on the underlying TLS channel. In affected versions, TLS certificate validation can be disabled when a proxy is configured, allowing an attacker who can intercept network traffic to supply a malicious update manifest and corresponding package with a matching hash. This can cause the client to download and install a tampered update, resulting in arbitrary code execution with the privileges of the GoSign Desktop user on Windows and macOS, or with elevated privileges on some Linux deployments. A local attacker who can modify proxy settings may also abuse this behavior to escalate privileges by forcing installation of a crafted update.
References
- ush.it/2025/11/14/multiple-vulnerabilities-gosign-desktop-remote-code-execution/ (opens in a new tab)
- infocert.digital/consumer/gosign-suite/ (opens in a new tab)
- vulncheck.com/advisories/gosign-desktop-insecure-update-mechanism-rce (opens in a new tab)
- ush.it/2025/11/14/vulnerabilita-multiple-gosign-desktop-esecuzione-remota-codice-arbitrario/ (opens in a new tab)