- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.0.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 11/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Axis2/Java fails to enforce the exposeServiceMetadata setting on several metadata routes, so services that had disabled it still disclose their metadata to anonymous callers. The exposed information includes operation names and request and response schemas, through routes such as packaged WSDL and XSD files, OpenAPI and Swagger UI endpoints, the services listing, and WS-MetadataExchange.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Maven packages
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.0.2.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
fixed in 2.0.2
fixed in 2.0.2
Evidence 5
- Advisory
- Patch
- Patch
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123779
Is CVE-2026-123779 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123779?
org.apache.axis2:axis2-transport-http (Maven): before 2.0.2. org.apache.axis2:axis2-openapi (Maven): before 2.0.2.Source: cve.now feed data
How do I fix CVE-2026-123779?
Upgrade to a fixed version: 2.0.2.Source: cve.now feed data