CVE-2026-63623: Red Hat Enterprise Linux 10 · Incorrect Permissions
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 8 Nov 2026, 23:24 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.5 |
|---|
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10libvirt | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6libvirt | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7libvirt | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8virt:rhel/libvirt | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9libvirt | Affected– | Fixed in– |
| Red Hat Enterprise Linux for NVIDIA 26libvirt | Affected– | Fixed in– |
AI-suggested
Red Hat currently does not offer an official fix or mitigation that meets their criteria for ease of use, applicability, or stability. Users should monitor the Red Hat advisory for updates. Until a fix is available, limiting local user access to the host system and avoiding untrusted users performing clone or convert operations may reduce risk. Customers with Red Hat Technical Account Managers (TAM) can seek direct guidance.
Description
A flaw was found in libvirt. During storage volume clone or convert operations, newly created volume images were temporarily world-readable. This was caused by the `qemu-img` utility running with overly permissive file creation settings, allowing any local user to read the full guest disk contents. This vulnerability could lead to sensitive information disclosure from guest virtual machines.