No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 23 Oct 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 23 Oct 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aiven-open
Aiven-open pghoard |
|
| Vendors & Products |
Aiven-open
Aiven-open pghoard |
Fri, 23 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pghoard is a PostgreSQL backup daemon and restore tooling that stores backup data in cloud object stores. Prior to version 2.7.2, an incomplete path traversal fix in pghoard allows an attacker with write access to the backup object storage (such as S3, GCS, or Azure) to execute arbitrary file writes and directory creation outside the designated PostgreSQL data directory (pgdata). When a database administrator executes a restore operation (via pghoard_restore get-basebackup), a maliciously crafted delta backup manifest with path traversal sequences (e.g., ../../../../etc/cron.d/backdoor) will write arbitrary payloads to the host system. This issue has been patched in version 2.7.2. | |
| Title | PGHoard: Incomplete Path Traversal fix in restore.py allows Arbitrary File Write | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-23T14:59:26.366Z
Reserved: 2026-07-15T16:54:55.816Z
Link: CVE-2026-63120
Updated: 2026-10-23T14:54:25.692Z
Status : Received
Published: 2026-10-23T13:17:12.010
Modified: 2026-10-23T15:17:34.400
Link: CVE-2026-63120
No data.
OpenCVE Enrichment
Updated: 2026-10-23T14:39:32Z