A "stack overwrite" vulnerability in GnuPG (gpg) 1.x before 1.4.6, 2.x before 2.0.2, and 1.9.0 through 1.9.95 allows attackers to execute ar
Noroxi assessment
Priority: Plan (action score 42/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 5.8% (FIRST EPSS); higher than 93.1% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: gnupg2 (Debian:12) 2.0.0-5.2; gnupg (Debian:3.1) 1.4.1-1.sarge6; gnupg (Red Hat:enterprise_linux:2.1::as) 0:1.0.7-20.
Add it to your regular patch cycle. Upgrade to gnupg2 (Debian:12) 2.0.0-5.2; gnupg (Debian:3.1) 1.4.1-1.sarge6; gnupg (Red Hat:enterprise_linux:2.1::as) 0:1.0.7-20 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A "stack overwrite" vulnerability in GnuPG (gpg) 1.x before 1.4.6, 2.x before 2.0.2, and 1.9.0 through 1.9.95 allows attackers to execute arbitrary code via crafted OpenPGP packets that cause GnuPG to dereference a function pointer from deallocated stack memory.
- Published
- Dec 7, 2006
- Updated
- Jun 16, 2026
- EPSS
- 5.8% · 93th percentile
- CWE
- —
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | privacy guard | cpe:2.3:a:gnu:privacy_guard |
| gpg4win | gpg4win | cpe:2.3:a:gpg4win:gpg4win |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | fedora core | cpe:2.3:o:redhat:fedora_core |
| redhat | linux advanced workstation | cpe:2.3:o:redhat:linux_advanced_workstation |
| rpath | linux | cpe:2.3:o:rpath:linux |
| slackware | slackware linux | cpe:2.3:o:slackware:slackware_linux |
| ubuntu | ubuntu linux | cpe:2.3:o:ubuntu:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu privacy guard1.2.4
- gnu privacy guard1.2.5
- gnu privacy guard1.2.6
- gnu privacy guard1.2.7
- gnu privacy guard1.3.3
- gnu privacy guard1.3.4
- gnu privacy guard1.4
- gnu privacy guard1.4.1
- gnu privacy guard1.4.2
- gnu privacy guard1.4.2.1
- gnu privacy guard1.4.2.2
- gnu privacy guard1.4.3
- gnu privacy guard1.4.4
- gnu privacy guard1.4.5
- gnu privacy guard1.9.10
- gnu privacy guard1.9.15
- gnu privacy guard1.9.20
- gnu privacy guard2.0
- gnu privacy guard2.0.1
- gpg4win gpg4win1.0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | gnupg2 | before 2.0.0-5.2 | 2.0.0-5.2 |
| Debian:3.1 | gnupg | before 1.4.1-1.sarge6 | 1.4.1-1.sarge6 |
| Red Hat:enterprise_linux:2.1::as | gnupg | before 0:1.0.7-20 | 0:1.0.7-20 |
| Red Hat:enterprise_linux:3::as | gnupg | before 0:1.2.1-19 | 0:1.2.1-19 |
| Red Hat:enterprise_linux:3::as | gnupg-debuginfo | before 0:1.2.1-19 | 0:1.2.1-19 |
| Red Hat:enterprise_linux:4::as | gnupg | before 0:1.2.6-8 | 0:1.2.6-8 |
| Red Hat:enterprise_linux:4::as | gnupg-debuginfo | before 0:1.2.6-8 | 0:1.2.6-8 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2003-0255The key validation code in GnuPG before 1.2.2 does not properly determine the validity of keys with multiple user IDs and assigns the greate42Plan
- CVE-2001-0522Format string vulnerability in Gnu Privacy Guard (aka GnuPG or gpg) 1.05 and earlier can allow an attacker to gain privileges via format str34Monitor
- CVE-2003-0978Format string vulnerability in gpgkeys_hkp (experimental HKP interface) for the GnuPG (gpg) client 1.2.3 and earlier, and 1.3.3 and earlier,31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2003-0971Dec 15, 2003 · GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption a21Monitor
- ← EarlierCVE-2006-0455Feb 15, 2006 · gpgv in GnuPG before 1.4.2.1, when using unattended signature verification, returns a 0 exit code in certain cases even when the detached si18Monitor
- ← EarlierCVE-2006-0049Mar 13, 2006 · gpg in GnuPG before 1.4.2.2 does not properly verify non-detached signatures, which allows attackers to inject unsigned data via a data pack21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:gnupg | 1.4.1-1.sarge6 · Debian:3.1 | Package registry (OSV) |
| debian:gnupg2 | 2.0.0-5.2 · Debian:12 | Package registry (OSV) |
| red hat:gnupg | 0:1.0.7-20 · Red Hat:enterprise_linux:2.1::as | Package registry (OSV) |
| red hat:gnupg-debuginfo | 0:1.2.1-19 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.gnupg.org/pipermail/gnupg-announce/2006q4/000491.html
- lists.suse.com/archive/suse-security-announce/2006-Dec/0004.html
- secunia.com/advisories/23245
- secunia.com/advisories/23250
- secunia.com/advisories/23255
- secunia.com/advisories/23259
- secunia.com/advisories/23269
- secunia.com/advisories/23284
- secunia.com/advisories/23290
- secunia.com/advisories/23299
- secunia.com/advisories/23303
- secunia.com/advisories/23329
- secunia.com/advisories/23335
- secunia.com/advisories/23513
- secunia.com/advisories/24047
- security.gentoo.org/glsa/glsa-200612-03.xml
- securitytracker.com/id?1017349
- support.avaya.com/elmodocs2/security/ASA-2007-047.htm
- www.debian.org/security/2006/dsa-1231
Vendor advisories and official records. Exploit/PoC links are deliberately left out.