Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
To mitigate this issue, ensure that the directory used for PostgreSQL data backups and the resulting archive have restrictive permissions. Administrators should configure their Ansible playbooks or manually adjust permissions to ensure the backup directory (e.g., `/var/backups/leapp`) is owned by root with `0700` permissions, and the backup archive itself has `0600` permissions. This prevents unauthorized local users from accessing sensitive PostgreSQL data. If the current task must be used as-is, restrict local-user access on affected systems and remove or re-permission the generated backup archive immediately after it is created. Always warn if there is a potential for reload and restarts.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 30 Jul 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in ansible-collection-redhat-leapp. When a remediation task is executed with elevated privileges and the `leapp_old_postgresql_data` option is selected, a PostgreSQL data backup archive is created with insecure permissions. This allows a local non-root user on the managed node to read sensitive archived PostgreSQL data, leading to information disclosure. | |
| Title | Ansible-collection-redhat-leapp: ansible-collection-redhat-leapp: information disclosure of postgresql data via insecure backup permissions | |
| First Time appeared |
Redhat
Redhat enterprise Linux |
|
| Weaknesses | CWE-732 | |
| CPEs | cpe:/o:redhat:enterprise_linux:10 cpe:/o:redhat:enterprise_linux:9 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-07-30T21:13:08.546Z
Reserved: 2026-07-30T20:29:28.829Z
Link: CVE-2026-68563
No data.
No data.
No data.
OpenCVE Enrichment
No data.