# CVE-2025-7425: Libxslt: libxml2: heap use-after-free in libxslt caused by atype corruption in xmlattrptr > Attackers can trigger heap corruption and potential code execution via crafted XSLT processing in the libxslt library. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jul 2025 - **Updated:** 15 Oct 2026 - **Also known as:** ALSA-2025:12447, ALSA-2025:12450, AZL-65409, AZL-73183, AZL-75182, BELL-CVE-2025-7425, BIT-java-2025-7425, BIT-java-min-2025-7425, BIT-jre-2025-7425, CLSA-2025-1754552192, CLSA-2025-1754552473, CLSA-2025-1754554806, CLSA-2025-1754649907, CLSA-2025-1758228035, CLSA-2025-1758228293, CLSA-2025-1758292868, CLSA-2025-1759336003, CLSA-2025-1759336205, CLSA-2025-1759336419, DEBIAN-CVE-2025-7425, DSA-5990-1, ECHO-511d-3254-a5d5, GHSA-8c4w-j52q-j4jq, MINI-wr59-6v6m-895x, RHSA-2025:12447, RHSA-2025:12450, RHSA-2025:13308, RHSA-2025:13309, RHSA-2025:13310, RHSA-2025:13311, RHSA-2025:13312, RHSA-2025:13313, RHSA-2025:13314, RHSA-2025:13464, RLSA-2025:12447, ROOT-OS-DEBIAN-11-CVE-2025-7425, ROOT-OS-UBUNTU-2404-CVE-2025-7425, SUSE-SU-2025:02547-1, SUSE-SU-2025:02617-1, SUSE-SU-2025:02620-1, SUSE-SU-2025:02621-1, SUSE-SU-2025:02758-1, UBUNTU-CVE-2025-7425, USN-7852-1, USN-7852-2, openSUSE-SU-2025:15363-1 ## What is CVE-2025-7425? CVE-2025-7425 is a high-severity use after free vulnerability in GNOME Compliance Operator 1, published on 10 Jul 2025. 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 libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2025-7425? 3 open source packages ship an affected version, including java, java-min and jre. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java` | Bitnami | All versions | 1.8.0, 8.0.481 | | `java-min` | Bitnami | All versions | 1.8.0, 8.0.481 | | `jre` | Bitnami | All versions | 1.8.0, 8.0.481 | | `libxml2` | AlmaLinux:8 | All versions | 2.9.7-21.el8_10.2 | | `libxml2-devel` | AlmaLinux:8 | All versions | 2.9.7-21.el8_10.2 | | `python3-libxml2` | AlmaLinux:8 | All versions | 2.9.7-21.el8_10.2 | | `libxml2` | AlmaLinux:9 | All versions | 2.9.13-11.el9_6 | | `libxml2-devel` | AlmaLinux:9 | All versions | 2.9.13-11.el9_6 | | `python3-libxml2` | AlmaLinux:9 | All versions | 2.9.13-11.el9_6 | | `libxml2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-21.el8_10.2 | | `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-21.el8_10.2 | | `python3-libxml2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-21.el8_10.2 | | `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-21.el8_10.2 | | `libxml2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-11.el9_6 | | `libxml2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-11.el9_6 | | `libxml2-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-11.el9_6 | | `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-11.el9_6 | | `libxml2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-11.el9_6 | | `libxml2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-11.el9_6 | | `libxml2-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-11.el9_6 | | `python3-libxml2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-11.el9_6 | | `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-11.el9_6 | | `libxml2-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2-devel` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.9.7-9.el8_2.4 | | `python3-libxml2-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.7-9.el8_2.4 | | `python3-libxml2` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.7-9.el8_2.4 | | `python3-libxml2-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.7-9.el8_2.4 | | `libxml2-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.9.7-9.el8_4.7 | | `libxml2-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.9.7-9.el8_4.7 | | `libxml2-devel` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.9.7-9.el8_4.7 | | `python3-libxml2-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.9.7-9.el8_4.7 | ## How do I fix CVE-2025-7425? Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.481. ## Is CVE-2025-7425 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7425 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-7425 and fix it if it is affected. What it is: CVE-2025-7425 is a high-severity use after free vulnerability in GNOME Compliance Operator 1, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7425 exists. Affected packages and fixed versions: - java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.481 - java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.481 - jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.481 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-7425/ (Markdown: https://insights.sbomify.com/CVE-2025-7425/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7425 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7425 - OSV: https://osv.dev/vulnerability/CVE-2025-7425 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-7425/ Summaries are generated and may contain mistakes; the official description above is the record.