# CVE-2025-7424: Libxslt: type confusion in xmlnode.psvi between stylesheet and source nodes > Type confusion in libxslt allows attackers to crash applications or corrupt memory via crafted XML transformations. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jul 2025 - **Updated:** 12 Oct 2026 - **Also known as:** AZL-65367, AZL-65406, BELL-CVE-2025-7424, BIT-java-2025-7424, BIT-java-min-2025-7424, BIT-jre-2025-7424, CLSA-2025-1765288229, DEBIAN-CVE-2025-7424, ECHO-c801-94c9-ac17, GHSA-w4gx-392p-5m58, MINI-q268-v77c-64c5, OESA-2025-1931, SUSE-SU-2025:20556-1, SUSE-SU-2025:20661-1, UBUNTU-CVE-2025-7424, USN-7945-1, openSUSE-SU-2025:15364-1 ## What is CVE-2025-7424? CVE-2025-7424 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion during XML transformations. This vulnerability allows an attacker to crash the application or corrupt memory. In some cases, it may lead to denial of service or unexpected behavior. Weakness: CWE-843 (Access of Resource Using Incompatible Type) ## Which versions are affected by CVE-2025-7424? 3 open source packages ship an affected version, including java, java-min and jre. It affects 3 products. | 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 | | `libxslt` | SUSE:Linux Micro 6.0 | All versions | 1.1.38-6.1 | | `libxslt` | SUSE:Linux Micro 6.1 | All versions | 1.1.38-slfo.1.1_4.1 | | `libxslt` | openSUSE:Tumbleweed | All versions | 1.1.43-2.1 | Products: Redhat Enterprise Linux, Redhat Openshift Container Platform, Xmlsoft Libxslt. ## How do I fix CVE-2025-7424? Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.481. ## Is CVE-2025-7424 being exploited? There is no known exploitation of CVE-2025-7424 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild) - [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8) - [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8) - [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8) - [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-7424 and fix it if it is affected. What it is: CVE-2025-7424 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-7424 in the wild and no public exploit code. 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-7424/ (Markdown: https://insights.sbomify.com/CVE-2025-7424/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7424 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7424 - OSV: https://osv.dev/vulnerability/CVE-2025-7424 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-7424/ Summaries are generated and may contain mistakes; the official description above is the record.