- 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.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Apache Axis2/Java is affected by a server-side request forgery flaw in how it handles WS-Addressing ReplyTo and FaultTo endpoints. An attacker can make the server connect to internal hosts or send response content to a host of their choosing.
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. An unauthenticated caller could supply a non-anonymous WS-Addressing wsa:ReplyTo or wsa:FaultTo address, and Axis2 would open a connection to that address to deliver the response or fault, allowing requests to internal hosts and delivery of response content to a host of the caller's choosing. From 2.0.2, decoupled responses are refused unless allowNonAnonymousResponseEndpoints is enabled, and enabled endpoints are restricted by scheme and screened at both the header-parsing and transport-selection layers. 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
- 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
- CVE published
- First seen by cve.now
- 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 6
- Advisory
- Patch
- Patch
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123753
Is CVE-2026-123753 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-123753?
org.apache.axis2:axis2-kernel (Maven): before 2.0.2.Source: cve.now feed data
How do I fix CVE-2026-123753?
Upgrade to a fixed version: 2.0.2.Source: cve.now feed data