CVE-2026-66713
Awaiting Analysis Awaiting Analysis - Queue

Remote Code Execution via Deserialization in Apache Axis2/Java

Vulnerability report for CVE-2026-66713, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-28

Last updated on: 2026-07-28

Assigner: Apache Software Foundation

Description

Deserialization of Untrusted Data (CWE-502) in the Tribes-based clustering component  in Apache Software Foundation Apache Axis2/Java through 2.0.0 on Apache Tomcat  (only when Tribes clustering is enabled, which is off by default) allows an  unauthenticated remote attacker with network access to the clustering port to  execute arbitrary code via a crafted serialized Java object delivered to the cluster  channel and deserialized in  org.apache.axis2.clustering.tribes.Axis2ChannelListener#messageReceived. Users are  recommended to upgrade to version 2.0.1, which fixes this issue by removing the  clustering feature entirely.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-28
Last Modified
2026-07-28
Generated
2026-07-28
AI Q&A
2026-07-28
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
apache axis2 to 2.0.1 (exc)
apache axis2 2.0.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a deserialization of untrusted data flaw (CWE-502) in Apache Axis2/Java through version 2.0.0. It exists in the Tribes-based clustering component but only when clustering is enabled, which is off by default. An unauthenticated remote attacker with network access to the clustering port can execute arbitrary code by sending a crafted serialized Java object to the cluster channel.

Detection Guidance

Check if Apache Axis2/Java with Tribes clustering enabled is running on your system. Look for open ports used by clustering (default is 4000). Use commands like netstat -tuln | grep 4000 or ss -tuln | grep 4000 to detect listening ports. Inspect Axis2 configuration files for clustering settings in axis2.xml.

Impact Analysis

If exploited, this vulnerability allows an attacker to execute arbitrary code on the affected system. This could lead to full system compromise, data theft, or further network infiltration. However, exploitation requires network access to the clustering port and the clustering feature must be enabled.

Compliance Impact

This vulnerability allows unauthenticated remote attackers to execute arbitrary code via crafted serialized Java objects, which could lead to unauthorized data access, modification, or exfiltration. Such risks may violate compliance requirements under GDPR (data protection) and HIPAA (health data security) by enabling breaches of confidentiality, integrity, or availability of sensitive data.

Mitigation Strategies

Upgrade Apache Axis2/Java to version 2.0.1 or later. If clustering is not required, disable Tribes clustering in axis2.xml by removing or commenting out clustering-related configurations. Block network access to clustering ports if clustering is enabled.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-66713. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart