CVE-2026-66713: 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
CVE-2026-66713 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Critical
- CVSS base score
- 9.8 (Apache), 8.1 (Red Hat)
- Weakness
- CWE-502
- Fixed releases
- Apache: 2.0.1
- Red Hat: 2.0.1
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-66713; each belongs to its advisory, not to every product listed. How records are collected and checked.
How do I fix CVE-2026-66713?
Upgrade to a fixed release named by the vendor:
- Apache: 2.0.1
- Red Hat: 2.0.1
- Users are recommended to upgrade to version 2.0.1, which fixes this issue by removing the clustering feature entirely. (Apache)
- No currently supported Red Hat product ships the affected Apache Axis2 Tribes clustering module, org.apache.axis2:axis2-clustering, so no mitigation action is required for Red Hat products. For any independently deployed or third party installation of Apache Axis2 through version 2.0.0 with Tribes clustering enabled, disabling the Tribes clustering feature, or restricting network access to the clustering port to trusted hosts only, removes the attack vector. This issue was corrected upstream in Apache Axis2 by removing the clustering feature entirely, so standalone Apache Axis2 deployments should upgrade to a corrected version. (Red Hat)
Vendor advisories for CVE-2026-66713
Apache
1 advisory- Advisory severityCritical9.8
Critical [CVE-2026-66713] 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
CVE-2026-66713Source published Source updated
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.
- Affected products in this advisory
- Apache Tomcat
- Apache Axis2
- Source-reported affected versions
- through 2.0.0
- Source-reported fixed versions
- 2.0.1
- Mitigation guidance
- Users are recommended to upgrade to version 2.0.1, which fixes this issue by removing the clustering feature entirely.
Red Hat
1 advisory- Advisory severityHigh8.1
High [CVE-2026-66713] Remote code execution via deserialization of untrusted data in Tribes clustering
CVE-2026-66713Source published Source updated
Remote code execution via deserialization of untrusted data in Tribes clustering. Red Hat rates this important (CVSS 8.1). Weakness: CWE-502.
- Related products — impact not confirmed
- No product details extracted. Check the source bulletin.
- Source-reported affected versions
- 2.0.0
- Source-reported fixed versions
- 2.0.1
- Mitigation guidance
- No currently supported Red Hat product ships the affected Apache Axis2 Tribes clustering module, org.apache.axis2:axis2-clustering, so no mitigation action is required for Red Hat products. For any independently deployed or third party installation of Apache Axis2 through version 2.0.0 with Tribes clustering enabled, disabling the Tribes clustering feature, or restricting network access to the clustering port to trusted hosts only, removes the attack vector. This issue was corrected upstream in Apache Axis2 by removing the clustering feature entirely, so standalone Apache Axis2 deployments should upgrade to a corrected version.
References
More Apache advisories
CVE-2026-120367Nov 9, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/JavaCVE-2026-123779Nov 9, 2026Direct Request ('Forced Browsing') vulnerability in Apache Axis2/JavaCVE-2026-123753Nov 9, 2026Server-Side Request Forgery (SSRF) vulnerability in Apache Axis2/JavaCVE-2026-123766Nov 9, 2026Apache Axis2 cross-site scripting (XSS)CVE-2026-123770Nov 9, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/JavaCVE-2026-120761Nov 9, 2026Apache Axis2 XXE
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
