CVE-2026-68563

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.

There's a Moderate flaw in ansible-collection-redhat-leapp allows local non-root users to read archived PostgreSQL data. The vulnerability occurs when a specific Leapp remediation task, intended to back up and remove old PostgreSQL data, creates a world-readable archive in /var/backups. Exploitation requires local access to a managed node where this particular remediation workflow has been executed and /var/lib/pgsql/data existed.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

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.