← AI agent vulnerabilities

CVE-2026-123779

5.3
Severity
Medium
Published
November 9, 2026
Last modified
November 12, 2026

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.

CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Weakness

References

CVE-2026-123779 on NVD

Listed in

MediumMCP servers

Related CVEs

Nov 16
CVE-2026-689348.7

code-review-mcp-server automates code review and can post comments directly on GitHub pull requests.

Nov 16
CVE-2026-1268165.5

Improper limitation of a pathname to a restricted directory in the cost report generation tool in AWS Pricing MCP Server (aws-pricing-mcp-server) before 1.0.31 might allow an actor who can influence the MCP…

Nov 16
CVE-2026-1266815.5

Improper restriction of intended endpoints in the connection configuration handling of the AWS Labs Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) before 0.0.19 might allow…

Nov 16
CVE-2026-1155637.5

OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server.

Nov 15
CVE-2026-1257717.2

Incorrect Privilege Assignment vulnerability in AtlasAiDev MCP Server for WordPress ai-workflow-automation-ai-agent-hub allows Privilege Escalation.This issue affects MCP Server for WordPress: from n/a…

Nov 13
CVE-2026-1263936.1

SiYuan before 3.8.10 contains a server-side request forgery vulnerability in the skill-install download path because fetchBytes performs only a parse-time hostname check instead of using ssrfSafeClient.