tool:gpgtar: Check the output directory with --directory.

F-GNUPG-001-002

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

gnupg/gnupgReported fixgnupg/gnupg

tool:gpgtar: Check the output directory with --directory.

fixed publicly

details

Finding IDs: F-GNUPG-001-002
Status: fixed publicly
Reported via: private reporting channel
Note: public GnuPG T8159 tracks gpgtar write outside --directory via symlink traversal with Reported-by: Oleh Konko; commit 7a2692fe5e58 landed on 2026-03-24 and GnuPG 2.5.19 announced the fix for gpgtar -C/--directory output-directory checking on 2026-04-24.

F-GNUPG-001-002: File / path escapes. gpgtar symlink traversal escapes the selected output directory. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-GNUPG-001-002

Security area (1seal assessment): Authorization. gpgtar checks that the requested extraction directory is empty and not a symlink before writing plaintext files. Reviewed 21 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.