# CVE-2025-12748: Libvirt: denial of service in xml parsing > A malicious user can cause a denial of service in libvirt by submitting crafted XML files that trigger excessive memory allocation before ACL checks. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **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:** 11 Nov 2025 - **Updated:** 29 Jun 2026 - **Also known as:** ALSA-2026:18326, ALSA-2026:18748, AZL-70187, AZL-70199, BELL-CVE-2025-12748, CLSA-2026-1779709803, CLSA-2026-1779871378, DEBIAN-CVE-2025-12748, GHSA-qwrw-p888-cc55, OESA-2025-2810, OESA-2025-2811, OESA-2025-2812, OESA-2025-2813, OESA-2025-2814, RHSA-2026:18326, RHSA-2026:18748, RLSA-2026:18326, RLSA-2026:18748, UBUNTU-CVE-2025-12748 ## What is CVE-2025-12748? CVE-2025-12748 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was discovered in libvirt in the XML file processing. More specifically, the parsing of user provided XML files was performed before the ACL checks. A malicious user with limited permissions could exploit this flaw by submitting a specially crafted XML file, causing libvirt to allocate too much memory on the host. The excessive memory consumption could lead to a libvirt process crash on the host, resulting in a denial-of-service condition. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2025-12748? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libvirt` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-client` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-client-qemu` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-common` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-config-network` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-config-nwfilter` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-interface` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-network` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-nodedev` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-nwfilter` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-qemu` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-secret` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-core` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-disk` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-iscsi` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-logical` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-mpath` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-rbd` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-driver-storage-scsi` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-kvm` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-lock` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-log` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-plugin-lockd` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-plugin-sanlock` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-daemon-proxy` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-devel` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-docs` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-libs` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-nss` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt-ssh-proxy` | AlmaLinux:10 | All versions | 11.10.0-12.el10_2.alma.1 | | `libvirt` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-client` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-client-qemu` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-daemon` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-daemon-common` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-daemon-config-network` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-daemon-config-nwfilter` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | | `libvirt-daemon-driver-interface` | AlmaLinux:9 | All versions | 11.10.0-12.el9_8.alma.1 | ## How do I fix CVE-2025-12748? Apply the vendor's patch. ## Is CVE-2025-12748 being exploited? There is no known exploitation of CVE-2025-12748 in the wild and no public exploit code. Public exploit code: - Proof of concept & details for CVE-2025-12748 (github_poc): https://github.com/TERESH1/CVE-2025-12748 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-12748 and fix it if it is affected. What it is: CVE-2025-12748 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 11 Nov 2025. 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-2025-12748 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-2025-12748/ (Markdown: https://insights.sbomify.com/CVE-2025-12748/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12748 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12748 - OSV: https://osv.dev/vulnerability/CVE-2025-12748 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-12748/ Summaries are generated and may contain mistakes; the official description above is the record.