CVE-2025-34324: GoSign Desktop versions 2.4.0 and earlier use an unsigned update manifest for distributing application updates

Q: How do I fix CVE-2025-34324?

gosign: upgrade to 2.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-34324 being exploited?

CVE-2025-34324 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-34324 affect?

CVE-2025-34324 affects gosign. Severity is high (CVSS 7.8). 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 unde

Q: How urgent is CVE-2025-34324?

Priority 33/100. High severity; Public exploit reference

Routine

HIGH 7.8UPGRADE

CVE-2025-34324 is a high-severity flaw (CVSS 7.8) affecting gosign. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-347
Published	2025-11-18
Last modified	2026-10-18

Publisher (CNA): VulnCheck · Vendor: infocert

Last updated 2026-10-18 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-11-18 17:16 UTCPublished CVE record published
2026-10-18 20:10 UTCUpdated Record last modified

infocert gosign UPGRADE

Affected: < 2.4.1

Fixed in: 2.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gosign || rpm -q gosign || gosign --version

2. UPGRADE to 2.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gosign

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gosign

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-34324?

gosign: upgrade to 2.4.1. Exact commands for each OS are on this page.

Is CVE-2025-34324 being exploited?

CVE-2025-34324 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-34324 affect?

CVE-2025-34324 affects gosign. Severity is high (CVSS 7.8). 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 unde

How urgent is CVE-2025-34324?

Priority 33/100. High severity; Public exploit reference

References

← Back to latest CVEs