Skip to main content
VulnerabilityPublished

CVE-2026-123779: Apache Axis2/Java · Forced Browsing

Affects Apache Axis2/JavaSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 2.0.2 when convenient.

Data as of 9 Nov 2026, 11:18 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.0.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Apache Axis2/Java and org.apache.axis2/axis2-transport-http and org.apache.axis2/axis2-openapi to 2.0.2.

Affected software

ProductAffectedFixed in
Apache Axis2/Javaorg.apache.axis2:axis2-transport-httpAffected
  • <2.0.2
Fixed in
  • 2.0.2
Apache Axis2/Javaorg.apache.axis2:axis2-openapiAffected
  • <2.0.2
Fixed in
  • 2.0.2
Mavenorg.apache.axis2/axis2-transport-httppkg:maven/org.apache.axis2/axis2-transport-httpOther threatsAffected
  • <2.0.2
Fixed in
  • 2.0.2
Mavenorg.apache.axis2/axis2-openapipkg:maven/org.apache.axis2/axis2-openapiOther threatsAffected
  • <2.0.2
Fixed in
  • 2.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Axis2/Java to version 2.0.2 or later, where this issue has been fixed. No other mitigation is indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…