CVE-2025-34324

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-11-18 17:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 7.0 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-11-18 17:16 UTC

Last modified

2026-10-18 20:10 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-347

Record status

Analyzed

Affected

• Infocert Gosign < 2.4.1

Attack profile CVSS 4.0 · 7.0

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

Passive

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-34324.md and follow it. Check whether this project is affected by CVE-2025-34324. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge