# CVE-2022-34169: Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets > An integer truncation flaw in Apache Xalan allows attackers to execute arbitrary Java bytecode via malicious XSLT stylesheets. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Jul 2022 - **Updated:** 27 May 2026 - **Also known as:** BIT-java-2022-34169, BIT-java-min-2022-34169, BIT-jre-2022-34169, CLEANSTART-2026-BP86310, CLEANSTART-2026-IS57850, CLSA-2026-1778028241, CLSA-2026-1784769537, DEBIAN-CVE-2022-34169, DLA-3155-1, DSA-5256-1, GHSA-9339-86wc-4qgf, OESA-2022-1977, RHLW-2026-cd97e66695607070, SUSE-RU-2024:3971-1, UBUNTU-CVE-2022-34169, openSUSE-SU-2024:13189-1 ## What is CVE-2022-34169? CVE-2022-34169 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. This can be used to corrupt Java class files generated by the internal XSLTC compiler and execute arbitrary Java bytecode. Users are recommended to update to version 2.7.3 or later. Note: Java runtimes (such as OpenJDK) include repackaged copies of Xalan. Weakness: CWE-681 (Incorrect Conversion between Numeric Types) ## Which versions are affected by CVE-2022-34169? 5 open source packages ship an affected version, including xalan:xalan, java and java-min. It affects 16 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `xalan:xalan` | Maven | All versions | 2.7.3 | | `xalan:xalan` | Maven | All versions | 2.7.3 | | `java` | Bitnami | From 1.8.0-333 to 1.8.0-333 | None | | `java-min` | Bitnami | From 1.8.0-333 to 1.8.0-333 | None | | `jre` | Bitnami | From 1.8.0-333 to 1.8.0-333 | None | | `apache-commons-lang3` | SUSE:Enterprise Storage 7.1 | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Enterprise Storage 7.1 | All versions | 6.10.0-150200.11.6.2 | | `netty3` | SUSE:Enterprise Storage 7.1 | All versions | 3.10.6-150200.3.13.2 | | `xalan-j2` | SUSE:Enterprise Storage 7.1 | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Enterprise Storage 7.1 | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 6.10.0-150200.11.6.2 | | `netty3` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 3.10.6-150200.3.13.2 | | `xalan-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 6.10.0-150200.11.6.2 | | `netty3` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 3.10.6-150200.3.13.2 | | `xalan-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 6.10.0-150200.11.6.2 | | `netty3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.10.6-150200.3.13.2 | | `xalan-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 6.10.0-150200.11.6.2 | | `netty3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.10.6-150200.3.13.2 | | `xalan-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.12.2-150200.3.10.2 | | `bcel` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 6.10.0-150200.11.6.2 | | `xalan-j2` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.16.0-150200.3.9.2 | | `bcel` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 6.10.0-150200.11.6.2 | | `xalan-j2` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.7.3-150200.11.7.1 | | `xerces-j2` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.12.2-150200.3.10.2 | | `apache-commons-lang3` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 3.16.0-150200.3.9.2 | | `netty3` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 3.10.6-150200.3.13.2 | | `netty3` | SUSE:Linux Enterprise Module for Development Tools 15 SP6 | All versions | 3.10.6-150200.3.13.2 | Products: Apache Xalan-Java, Azul Zulu, Debian Debian Linux, Fedoraproject Fedora, Netapp 7-Mode Transition Tool, Netapp Active Iq Unified Manager, Netapp Cloud Insights Acquisition Unit, Netapp Cloud Secure Agent, Netapp Hci Compute Node, Netapp Hci Management Node, Netapp Oncommand Insight, Netapp Solidfire, Oracle Graalvm, Oracle Jdk, Oracle Jre, Oracle Openjdk. ## How do I fix CVE-2022-34169? Upgrade xalan:xalan to 2.7.3 or later. ## Is CVE-2022-34169 being exploited? There is no known exploitation of CVE-2022-34169 in the wild and no public exploit code. Public exploit code: - cve-2022-34169 延伸出的Jdk Xalan的payload自动生成工具，可根据不同的Jdk生成出其所对应的xslt文件 (github_poc): https://github.com/flowerwind/AutoGenerateXalanPayload - A PoC for CVE-2022-34169, for the SU_PWN challenge from SUCTF 2025 (github_poc): https://github.com/Disnaming/CVE-2022-34169 - https://nvd.nist.gov/vuln/detail/CVE-2022-34169 (github_poc): https://github.com/bor8/CVE-2022-34169 ## Other vulnerabilities in Debian Debian Linux - [CVE-2014-0107](https://insights.sbomify.com/CVE-2014-0107/): Improper Authorization in Apache Xalan-Java (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-34169 and fix it if it is affected. What it is: CVE-2022-34169 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jul 2022. 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-2022-34169 in the wild and no public exploit code. Affected packages and fixed versions: - xalan:xalan (Maven): affected all versions; fixed in 2.7.3 - xalan:xalan (Maven): affected all versions; fixed in 2.7.3 - java (Bitnami): affected from 1.8.0-333 up to 1.8.0-333; no fix listed - java-min (Bitnami): affected from 1.8.0-333 up to 1.8.0-333; no fix listed - jre (Bitnami): affected from 1.8.0-333 up to 1.8.0-333; no fix listed 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-2022-34169/ (Markdown: https://insights.sbomify.com/CVE-2022-34169/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34169 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34169 - OSV: https://osv.dev/vulnerability/CVE-2022-34169 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-34169/ Summaries are generated and may contain mistakes; the official description above is the record.