Skip to main content
VulnerabilityPublished

CVE-2026-120832: Apache Axis2/Java · Server-Side Request Forgery (SSRF) Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120832· High

Not known to be exploited : upgrade to 2.0.2 soon.

Data as of 9 Nov 2026, 13:17 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.0.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Axis2/Java and org.apache.axis2/axis2-kernel to 2.0.2.

Affected software

ProductAffectedFixed in
Apache Axis2/Javaorg.apache.axis2:axis2-kernelAffected
  • <2.0.2
Fixed in
  • 2.0.2
Mavenorg.apache.axis2/axis2-kernelpkg:maven/org.apache.axis2/axis2-kernelOther threatsAffected
  • <2.0.2
Fixed in
  • 2.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Axis2/Java to version 2.0.2 or later, where this SSRF vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in Apache Axis2/Java versions through 2.0.1. The vulnerability allows an attacker who controls a WSDL or schema processed by an Axis2 application to cause the JVM to send requests to arbitrary internal or external hosts by exploiting the lack of scheme or host restrictions when fetching absolute URLs in wsdl:import locations and schemaLocations. This issue is fixed in version 2.0.2.

References

Community reviews

Loading reviews…