CVE-2026-123753: Apache Axis2/Java · Server-Side Request Forgery (SSRF) Vulnerability
Source GCVE Database
Not known to be exploited : upgrade to 2.0.2 soon.
Data as of 9 Nov 2026, 13:05 UTC
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
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Apache Axis2/Javaorg.apache.axis2:axis2-kernel | Affected
| Fixed in
|
Mavenorg.apache.axis2/axis2-kernelpkg:maven/org.apache.axis2/axis2-kernelOther threats | Affected
| Fixed in
|
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 vulnerability is fixed. Version 2.0.2 refuses decoupled responses by default unless allowNonAnonymousResponseEndpoints is explicitly enabled, and applies strict endpoint restrictions. No other mitigation is recommended as the fix is available.
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in Apache Axis2/Java versions through 2.0.1. An unauthenticated attacker can supply a non-anonymous WS-Addressing ReplyTo or FaultTo address, causing Axis2 to open connections to arbitrary internal hosts and deliver response content to an attacker-controlled host. This behavior is fixed starting in version 2.0.2 by refusing decoupled responses unless explicitly enabled and restricting allowed endpoints by scheme and header/transport validation.
References
- nvd.nist.gov/vuln/detail/CVE-2026-123753 (opens in a new tab)
- github.com/apache/axis-axis2-java-core/commit/1671a68660df39459bf22f7b00309e2a8e782117 (opens in a new tab)
- github.com/apache/axis-axis2-java-core/commit/1b6856b4d7903780786c79327bed1b53ea051a15 (opens in a new tab)
- axis.apache.org/axis2/java/core/release-notes/2.0.2.html (opens in a new tab)
- lists.apache.org/thread.html/rddzl5jfmlr09yr9qj33by7kzprwwvnc (opens in a new tab)
- openwall.com/lists/oss-security/2026/11/06/23 (opens in a new tab)