Skip to main content
← Vulnerabilities

Apache Axis2/Java: SSRF via WSDL/XSD schema import resolution

Exploited
No known exploitation
Fix
Fixed in 2.0.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.0.2.

Published
Last modified
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Apache Axis2/Java is affected by a server-side request forgery flaw in how it fetches WSDL and schema imports when building service descriptions. An attacker who controls a WSDL or schema processed by an Axis2 application could make the server send requests to arbitrary internal or external hosts.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Server-Side Request Forgery (SSRF) vulnerability in Apache Axis2/Java. When Axis2 built a service description from a WSDL, through ServiceClient, AxisService.createClientSideAxisService or WSDLToAxisServiceBuilder, it fetched the absolute URLs in wsdl:import locations and in xsd:import and xsd:include schemaLocations with no scheme or host restriction; the AAR and WAR deployment resolvers also passed absolute schema locations on to the network. An attacker who controls a WSDL or schema processed by an Axis2 application could therefore make the JVM send requests to arbitrary internal or external hosts. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Impact

  • Widely used

    168 packages depend on org.apache.axis2:axis2-kernel.Source: deps.dev

What to do

  • Upgrade to a fixed version: 2.0.2.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • fixed in 2.0.2

    Fixed in 2.0.2 (released Oct 29, 2026, 11 days before disclosure).

    The latest release, 2.0.2, is not affected.

Evidence 4

  1. Advisory
  2. Patch
  3. Link
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-120832

Is CVE-2026-120832 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120832?

org.apache.axis2:axis2-kernel (Maven): before 2.0.2.Source: cve.now feed data

How do I fix CVE-2026-120832?

Upgrade to a fixed version: 2.0.2.Source: cve.now feed data