CVE-2022-34169

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 11.0%, top 6% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 18%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
96.8%
KEV
Not listed

Published

July 19, 2022

Last Modified

May 27, 2026

References (48)

Vendor Advisories for CVE-2022-34169(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-xalan-j2-0:2.7.1-26.redhat_00015.1.ep7.el72024-11-25redhat
redhatxalan2024-11-04redhat
redhateap8-wildfly-0:8.0.4-2.GA_redhat_00005.1.el8eap2024-11-04redhat
redhateap8-wildfly-0:8.0.4-2.GA_redhat_00005.1.el9eap2024-11-04redhat
redhateap7-xalan-j2-0:2.7.1-37.redhat_00015.1.el8eap2024-10-14redhat
redhateap7-xalan-j2-0:2.7.1-37.redhat_00015.1.el7eap2024-10-14redhat
redhateap7-xalan-j2-0:2.7.1-37.redhat_00015.1.el9eap2024-10-14redhat
redhatpatch2022-07-28redhat
redhatpatch2022-07-28redhat
redhatpatch2022-07-28redhat
redhatpatch2022-07-28redhat
redhatWindows2022-07-28redhat
redhatLinux2022-07-28redhat
redhatjava-17-openjdk-1:17.0.4.0.8-2.el9_02022-07-27redhat
redhatjava-17-openjdk-1:17.0.4.0.8-2.el8_62022-07-26redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-1.el8_12022-07-25redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el9_02022-07-25redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-2.el8_62022-07-25redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-1.el7_92022-07-25redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-1.el8_42022-07-25redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-1.el9_02022-07-25redhat
redhatjava-1.8.0-openjdk-1:1.8.0.342.b07-1.el8_22022-07-25redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el8_42022-07-21redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el8_12022-07-21redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el8_62022-07-21redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el7_92022-07-21redhat
redhatjava-11-openjdk-1:11.0.16.0.8-1.el8_22022-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
xalan:xalan2.1.0 ... 2.7.2 (11 versions)2.7.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:08 UTCEPSS rescore
  3. 2026-07-08 15:12 UTCEPSS rescore
  4. 2026-07-07 13:44 UTCEPSS rescore
  5. 2026-07-05 02:28 UTCEPSS rescore
  6. 2026-07-01 15:04 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-28 23:32 UTCOSV refresh
  10. 2026-06-28 14:06 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-25 13:48 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-21 14:55 UTCEPSS rescore
  22. 2026-06-21 14:55 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-19 19:24 UTCEPSS rescore
Show 49 more
  1. 2026-06-19 19:24 UTCEPSS rescore
  2. 2026-06-18 17:51 UTCEPSS rescore
  3. 2026-06-18 17:51 UTCEPSS rescore
  4. 2026-06-17 17:51 UTCEPSS rescore
  5. 2026-06-17 17:51 UTCEPSS rescore
  6. 2026-06-16 17:51 UTCEPSS rescore
  7. 2026-06-15 17:46 UTCEPSS rescore
  8. 2026-06-14 23:15 UTCEPSS rescore
  9. 2026-06-13 22:58 UTCEPSS rescore
  10. 2026-06-12 23:10 UTCEPSS rescore
  11. 2026-06-12 23:10 UTCEPSS rescore
  12. 2026-06-11 19:55 UTCOSV refresh
  13. 2026-06-11 13:58 UTCEPSS rescore
  14. 2026-06-11 13:58 UTCEPSS rescore
  15. 2026-06-10 22:17 UTCEPSS rescore
  16. 2026-06-10 13:20 UTCEPSS rescore
  17. 2026-06-08 14:15 UTCEPSS rescore
  18. 2026-06-08 14:15 UTCEPSS rescore
  19. 2026-06-07 15:23 UTCEPSS rescore
  20. 2026-06-07 15:23 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 22:45 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-04 13:11 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-02 20:11 UTCEPSS rescore
  29. 2026-06-01 13:50 UTCEPSS rescore
  30. 2026-06-01 13:50 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 22:29 UTCEPSS rescore
  33. 2026-05-31 22:29 UTCEPSS rescore
  34. 2026-05-31 00:15 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-29 13:43 UTCEPSS rescore
  37. 2026-05-29 13:43 UTCEPSS rescore
  38. 2026-05-28 13:43 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-27 13:39 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-26 13:43 UTCEPSS rescore
  43. 2026-05-26 13:43 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-26 07:17 UTCEPSS rescore
  47. 2026-05-25 18:42 UTCEG score recompute
  48. 2026-05-25 18:42 UTCVendor advisory
  49. 2026-05-24 16:51 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCDisnaming/CVE-2022-34169
    First seen Jan 17, 2025

    A PoC for CVE-2022-34169, for the SU_PWN challenge from SUCTF 2025

    Open source ↗
  • GitHub PoCflowerwind/AutoGenerateXalanPayload
    First seen Jan 17, 2023

    cve-2022-34169 延伸出的Jdk Xalan的payload自动生成工具，可根据不同的Jdk生成出其所对应的xslt文件

    Open source ↗

Frequently asked(5)

What is CVE-2022-34169?
CVE-2022-34169 is a high vulnerability published on July 19, 2022. 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…
When was CVE-2022-34169 disclosed?
CVE-2022-34169 was first published in the National Vulnerability Database on July 19, 2022, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-34169 actively exploited?
CVE-2022-34169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-34169?
CVE-2022-34169 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-34169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-34169, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-34169

Explore →

Is Your Infrastructure Affected by CVE-2022-34169?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs