Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-9339-86wc-4qgf

Apache Xalan Java XSLT library integer truncation issue when processing malicious XSLT stylesheets

CVSS 7.5 HighCriticalEPSS 0.82 · 99th percentile

Critical, because:

  • CVSS score 7.5 (7.0 or more) and EPSS 0.82 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 20 Jul 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
xalan:xalanMaven<2.7.32.7.3
Identifiers
GHSA-9339-86wc-4qgf · BIT-java-2022-34169 · BIT-java-min-2022-34169 · BIT-jre-2022-34169 · CVE-2022-34169
Weakness (CWE)
CWE-681
Tags
Published
20 Jul 2022
Updated
8 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Xalan Java (xalan:xalan) versions before 2.7.3 are vulnerable. An attacker who can supply a malicious XSLT stylesheet for processing can trigger an integer truncation that corrupts Java class files generated by the internal XSLTC compiler, allowing execution of arbitrary Java bytecode. Upgrade to xalan:xalan 2.7.3 or later.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.82, the 99th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.