# CVE-2026-68563: Information disclosure in Red Hat Enterprise Linux 10

> A local non-root user can read sensitive PostgreSQL data due to insecure permissions on backup archives created by the Leapp collection.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-5qhg-ffgw-hh79

## What is CVE-2026-68563?

CVE-2026-68563 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-68563?


## How do I fix CVE-2026-68563?

Apply the vendor's patch.

## Is CVE-2026-68563 being exploited?

There is no known exploitation of CVE-2026-68563 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68563 and fix it if it is affected.

What it is: CVE-2026-68563 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68563 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68563/ (Markdown: https://insights.sbomify.com/CVE-2026-68563/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68563
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68563
- OSV: https://osv.dev/vulnerability/CVE-2026-68563

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68563/
Summaries are generated and may contain mistakes; the official description above is the record.