Medium [CVE-2026-68563] Information disclosure of PostgreSQL data via insecure backup permissions
This medium-severity Red Hat Linux advisory covers CVE-2026-68563 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat package: ansible-collection-redhat-leapp.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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. 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. Red Hat severity: Moderate — CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Weakness: CWE-732. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9.
Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: ansible-collection-redhat-leapp.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 10 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.