CVE-2025-34324: GoSign Desktop < 2.4.1 Insecure Update Mechanism RCE

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2025-11-18 · updated 2026-10-18
Weakness: CWE-347

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.

Affected products

Tinexta InfoCert S.p.A. GoSign Desktop: before 2.4.1 — fixed in 2.4.1

How to fix

Upgrade to a fixed version: Tinexta InfoCert S.p.A. GoSign Desktop 2.4.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-34324 or the next vulnerability affects your stack