Quick answers
- Is CVE-2026-123753 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123753 being exploited in the wild.
- How severe is CVE-2026-123753?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Axis2/Java through 2.0.1.
- Is there a fix for CVE-2026-123753?
- Yes: fixed in 2.0.2. Until then: In Axis2 2.0.2+, decoupled WS-Addressing responses are refused by default. If a deployment requires decoupled responses, enable the allowNonAnonymousResponseEndpoints parameter and configure httpFrontendHostUrl to restrict reply addresses to trusted hosts. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123753 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123753?
- Check whether you run Apache Axis2/Java at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.2
In Axis2 2.0.2+, decoupled WS-Addressing responses are refused by default. If a deployment requires decoupled responses, enable the allowNonAnonymousResponseEndpoints parameter and configure httpFrontendHostUrl to restrict reply addresses to trusted hosts.
Technical details
This SSRF vulnerability occurs in WS-Addressing decoupled response handling: an unauthenticated attacker can set non-anonymous wsa:ReplyTo or wsa:FaultTo addresses to redirect response traffic to internal hosts. Axis2 versions through 2.0.1 do not validate or restrict these addresses at the transport layer. Exploitation requires only network access to the SOAP endpoint; no authentication or user interaction is needed.
Affected products
- Apache Axis2/Java through 2.0.1
Timeline
- 2026-11-09: disclosed