PatchTheCVEgpg4win vulnerabilities and fixes
Recent CVEs affecting gpg4win, with upgrade or downgrade steps. 3 tracked.
gpg4win has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-01-27. Highest priority: CVE-2026-24881 (score 58/100).
- CVE-2026-24882 HIGH 8.4 UPGRADE UPGRADE In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT co
- CVE-2026-24881 HIGH 8.1 UPGRADE UPGRADE In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key
- CVE-2026-24883 LOW 3.7 UPGRADE UPGRADE In GnuPG before 2.5.17, a long signature packet length causes parse_signature to return success with sig->data
FAQ
How do I fix gpg4win vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is gpg4win being exploited right now?
None of the tracked gpg4win CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gpg4win CVE should I patch first?
CVE-2026-24881 currently ranks highest (58/100): In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key.