cve.bz

CVE-2026-66713 apache axis2\/java: Deserialization of Untrusted Data

9.8 criticalEPSS 1.7%Fix available

Critical (9.8) in apache axis2\/java. EPSS 1.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.7% (unchanged from 1.7% a week ago; 1.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 78th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-66713 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-66713?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-66713?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-66713 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-66713

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-66713](https://cve.bz/cve/badge/CVE-2026-66713.svg)](https://cve.bz/cve/CVE-2026-66713)

HTML:

<a href="https://cve.bz/cve/CVE-2026-66713"><img src="https://cve.bz/cve/badge/CVE-2026-66713.svg" alt="CVE-2026-66713"></a>

Affected

  • apache:axis2\/java

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Axis2/Javathrough 2.0.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw affects the Tribes based clustering feature of Apache Axis2/Java, which is disabled by default and only reachable when an administrator has explicitly enabled Tribes clustering and exposed the clustering port to untrusted networks. Exploitation requires the vulnerable org.apache.axis2:axis2-clustering module, containing org.apache.axis2.clustering.tribes.Axis2ChannelListener, to be present on the classpath. Red Hat has reviewed its supported product portfolio and confirmed that no currently shipping Red Hat product includes the Axis2 Tribes clustering module. Some Red Hat products bundle other, unrelated Apache Axis2 components, for example JAX-WS and kernel support jars, but these do not include the vulnerable clustering listener and are therefore not affected by this issue. Apache Tomcat itself, which some Red Hat products ship, is also not affected, as the vulnerable deserialization code resides entirely within Apache Axis2, not within Tomcat.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10tomcatNot affected
Red Hat Enterprise Linux 10tomcat9Not affected
Red Hat Enterprise Linux 6tomcat6Not affected
Red Hat Enterprise Linux 7tomcatNot affected
Red Hat Enterprise Linux 8tomcatNot affected
Red Hat Enterprise Linux 9tomcatNot affected
Red Hat Hardened Imagestomcat10Not affected
Red Hat Hardened Imagestomcat11Not affected
Red Hat JBoss Enterprise Application Platform Expansion Packaxis2-kernelNot affected
Red Hat JBoss Web Server 5jws5-tomcatNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-66713.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON