CVE-2026-66713
Unauthenticated RCE via deserialization in Axis2 Tribes clustering (cluster port).
Is CVE-2026-66713 being exploited?
Not confirmed. CVE-2026-66713 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-66713?
CVE-2026-66713 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-66713?
Yes. A fix has been recorded for CVE-2026-66713. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66713 affect?
CVE-2026-66713 affects Apache Axis2/Java <= 2.0.0 (Tribes clustering enabled), Apache Tomcat hosting vulnerable Axis2 deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66713?
Upgrade to Axis2 2.0.1 or disable/remove Tribes clustering; block cluster port.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution via crafted serialized Java object on the Axis2 cluster port, potentially allowing full system compromise.
Immediate action required
- affected<= 2.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.