Quick answers
- Is CVE-2026-123779 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123779 being exploited in the wild.
- How severe is CVE-2026-123779?
- 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-123779?
- Yes: fixed in 2.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123779 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123779?
- 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
Technical details
The exposeServiceMetadata parameter was enforced only on ?wsdl, ?wsdl2, and ?xsd queries. Multiple other metadata disclosure paths—including packaged .wsdl/.xsd file routes, ?wsdl=NAME queries, OpenAPI/Swagger UI endpoints, the services listing, WS-MetadataExchange GetMetadata, and the ping module—bypassed this check, leaking operation names and request/response schemas to unauthenticated callers. This is an access control bypass requiring only network access to affected endpoints.
Affected products
- Apache Axis2/Java through 2.0.1
Timeline
- 2026-11-09: disclosed