Vulnerability in ansible-collection-redhat-leapp (CVE-2026-68563)
Summary
Vulnerability in ansible-collection-redhat-leapp (CVE-2026-68563). Confidential information can be exposed externally. Exploitable via leapp_old_postgresql_data.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-68563 has been found in ansible-collection-redhat-leapp.
Attackers can target a specific entry point like leapp_old_postgresql_data over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ansible-collection-redhat-leapp CVE-2026-68563" on the vendor's site.
CVE-2026-68563 (ansible-collection-redhat-leapp) — CWE-732 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: leapp_old_postgresql_data
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-732) exists in ansible-collection-redhat-leapp. Attackers reach the vulnerable code path via leapp_old_postgresql_data.
Check the vendor advisory for the affected versions of ansible-collection-redhat-leapp. Attack surface: leapp_old_postgresql_data.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ansible-collection-redhat-leapp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ansible-collection-redhat-leapp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ansible-collection-redhat-leappを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web secalert@redhat.com
- web secalert@redhat.com
- web nvd.nist.gov
- web github.com