Vulnerability in GnuPG (CVE-2025-68973)
Summary
Vulnerability in GnuPG (CVE-2025-68973). Confidential information can be exposed externally.
Original description
The description as published by the source.
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-68973 has been found in GnuPG.
Confidential information can be exposed externally. CVSS score: 7.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GnuPG CVE-2025-68973" on the vendor's site.
CVE-2025-68973 (GnuPG) — CWE-675 / CVSS v3 7.8
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-675) exists in GnuPG.
Check the vendor advisory for the affected versions of GnuPG.
Severity: High (CVSS 7.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'GnuPG' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'GnuPG' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
GnuPGを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2025-68973 gnupg Fixed in: 2.4.9-r0
- Debian DEBIAN-CVE-2025-68973 gnupg2 Fixed in: 2.2.27-2+deb11u3
References
- issue cve@mitre.org
- issue cve@mitre.org
- mailing cve@mitre.org
- patch cve@mitre.org
- patch cve@mitre.org
- patch openwall.com
- web cve@mitre.org
- web gpg.fail
- web lists.debian.org