# CVE-2026-123779: Apache Axis2/Java metadata exposure in forced browsing

Source: https://junglewise.ai/threats/cve-2026-123779-direct-request-forced-browsing-vulnerability-in-apache-axis2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-123779 · Severity: info · Published 2026-11-09

Apache Axis2 is a web services framework that processes SOAP and REST requests. When a service administrator disabled metadata exposure via the exposeServiceMetadata parameter, Axis2 failed to enforce this setting on several endpoints, allowing anonymous attackers to discover service operation names and data schemas that should have been hidden.

Technologies: [Apache Axis2/Java](https://junglewise.ai/threats/technologies/apache-axis2-java). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://axis.apache.org/axis2/java/core/release-notes/2.0.2.html](https://axis.apache.org/axis2/java/core/release-notes/2.0.2.html)

## Related threats

- [Apache Axis2/Java unrestricted resource allocation in form data parsing](https://junglewise.ai/threats/cve-2026-123770-allocation-of-resources-without-limits-or-throttling)
- [Apache Axis2/Java XSS in OpenAPI module Host header](https://junglewise.ai/threats/cve-2026-123766-improper-neutralization-of-input-during-web-page-generation)
- [Apache Axis2 Server-Side Request Forgery via WS-Addressing](https://junglewise.ai/threats/cve-2026-123753-server-side-request-forgery-ssrf-vulnerability-in-apache-axis2)