# CVE-2026-105712: Path traversal in GnuPG

> Attackers can overwrite files outside the extraction directory via symlink following in gpgtar when using the --directory option.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** AZL-105962, BELL-CVE-2026-105712, CLSA-2026-1791488683, DEBIAN-CVE-2026-105712, ECHO-7e32-d187-cc5e, GHSA-9w76-549g-prc8, OESA-2026-4360, OESA-2026-4361, OESA-2026-4362, OESA-2026-4363, RHSA-2026:77484, UBUNTU-CVE-2026-105712

## What is CVE-2026-105712?

CVE-2026-105712 is a low-severity path traversal vulnerability in GnuPG, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

gpgtar in GnuPG before 2.5.19 can allow file overwrite via crafted data in an archive. When extracting an untrusted archive with --directory (aka -C) into an existing directory containing a pre-existing symlink, gpgtar can follow that symlink and create or overwrite a file outside the selected extraction directory. The write is limited by the extraction user's filesystem permissions. An archive extracted into a fresh empty directory does not have this risk.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-105712?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnupg2` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-dirmngr` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-g13` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-gpg-agent` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-gpgconf` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-keyboxd` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-scdaemon` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-smime` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-utils` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-verify` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |
| `gnupg2-wks` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.1.hum1 |

## How do I fix CVE-2026-105712?

Upgrade to a fixed version.

## Is CVE-2026-105712 being exploited?

There is no known exploitation of CVE-2026-105712 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105712 and fix it if it is affected.

What it is: CVE-2026-105712 is a low-severity path traversal vulnerability in GnuPG, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-105712 in the wild and no public exploit code.

Affected product: GnuPG. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105712/ (Markdown: https://insights.sbomify.com/CVE-2026-105712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105712
- OSV: https://osv.dev/vulnerability/CVE-2026-105712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105712/
Summaries are generated and may contain mistakes; the official description above is the record.