Skip to content
Fencer Intel
low —

CVE-2026-123779 json

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

published 2d ago modified 2d ago also EUVD-2026-119978

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.axis2:axis2-transport-http 2.0.2
  • maven org.apache.axis2:axis2-openapi 2.0.2
  • Apache Software Foundation Apache Axis2/Java 2.0.2

Is CVE-2026-123779 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected packages

ecosystem package affected fixed in
maven org.apache.axis2:axis2-transport-http
<2.0.2
2.0.2
maven org.apache.axis2:axis2-openapi
<2.0.2
2.0.2

Affected products

  • Apache Software Foundation Apache Axis2/Java

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.