CVE-2026-123779

published 9 Nov 2026 · updated 12 Nov 2026

Apache Axis2/Java: exposeServiceMetadata not enforced on all metadata routes

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.0.2.

Direct Request ('Forced Browsing') vulnerability in Apache Axis2/Java. The exposeServiceMetadata service parameter was enforced only on the ?wsdl, ?wsdl2 and ?xsd queries. For a service that had disabled it, the packaged .wsdl and .xsd file routes, the named-WSDL ?wsdl=NAME route of the standalone HTTP server, the OpenAPI, Swagger UI and MCP catalog endpoints, the services listing, WS-MetadataExchange GetMetadata and the ping module still disclosed its metadata to anonymous callers, including operation names and request and response schemas. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation<2.0.22.0.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-123779 severity on Zeptric[![CVE-2026-123779](https://zeptric.io/badge/cve/CVE-2026-123779.svg)](https://zeptric.io/cve/CVE-2026-123779)