Skip to content
major vulnerability· requires attention

Affects Apache Struts, a widely used enterprise web framework; exploit could impact many apps across industries.

Web

CVE-2025-68493

8.1
High
EPSS 43%Patch availableJan 12, 2026

Missing XML Validation in Apache Struts may allow crafted XML abuse.

common questions

Is CVE-2025-68493 being exploited?

Not confirmed. CVE-2025-68493 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 43% probability of exploitation in the next 30 days.

How severe is CVE-2025-68493?

CVE-2025-68493 is rated High with a CVSS score of 8.1. 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-2025-68493?

Yes. A fix has been recorded for CVE-2025-68493. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-68493 affect?

CVE-2025-68493 affects Apache Struts 2.x (versions 2.0.0-2.2.1, 2.2.1-6.1.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-68493?

Upgrade to Struts 6.1.1+

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Struts 2.x (versions 2.0.0-2.2.1, 2.2.1-6.1.0)
impact

XML parsing abuse could lead to data exposure or service disruption, depending on parser/config.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Struts
  • affected>= 2.0.0 and < 2.2.1
  • affected>= 2.2.1 and <= 6.1.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free