Skip to content

CVE-2026-129448

Apache Roller XML-RPC deserialization allows unauthenticated remote code execution (CVE-2026-129448)

Critical 9.8 KEV Published

Apache Roller 4.0.0 through 6.1.4 has a critical unauthenticated remote code execution flaw in its XML-RPC endpoint. CISA KEV lists it as actively exploited. Upgrade to 6.1.6 or later, or apply Apache's workaround.

What happened

Apache Roller's XML-RPC endpoint accepts vendor extension types and deserialises them before authenticating the requester. An unauthenticated attacker can send a specially crafted XML-RPC request that leads to arbitrary code execution on the server. The CVSS v3.1 vector scores this as 9.8 critical: network reachable, low complexity, no privileges and no user interaction. CISA's KEV entry added the flaw on 20 November 2026 and, together with CISA's SSVC assessment, lists it as actively exploited. No vendor exploitation statement is included in the record.

Who is affected

Apache Roller versions 4.0.0 through 6.1.4 are affected. The CVE record notes this is the same vulnerability as CVE-2026-82384, which listed Apache Roller 6.1.5 as affected. Apache Roller is a Java-based blog and content management platform; the vulnerable path is the /roller-services/xmlrpc endpoint. The XML-RPC endpoint is reachable over the network without credentials, so any instance that can be reached by untrusted users should be treated as exposed until the upgrade or mitigation is applied.

What to do now

  1. Upgrade to Apache Roller 6.1.6 or later. Apache's guidance in the CVE record says that release disables the vendor extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. The CVE record also lists 6.1.5 as a fixed version, but the Apache text recommends 6.1.6 or later, so that is the safer upgrade target.
  2. If you cannot upgrade immediately, apply the documented mitigation: set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialise the request before checking that setting.
  3. Restrict network access to the XML-RPC endpoint until the upgrade or mitigation is in place, and confirm whether the Roller instance needs to be reachable from the internet at all.
  4. For US federal stakeholders, CISA's KEV entry sets a due date of 23 November 2026 and requires applying mitigations in accordance with vendor instructions, following CISA's BOD 26-04 patching guidance.

How to detect it

The CVE record does not include vendor-supplied indicators of compromise. Because the vulnerable path is /roller-services/xmlrpc, review web server and application logs for unexpected POST requests to that endpoint, especially from internet-facing hosts. Investigate requests containing XML-RPC extension type parameters or deserialisation errors around that path. If the XML-RPC feature is not required, treat unusual requests to /roller-services/xmlrpc as a reason to inspect the host.

Beyond the patch

Beyond the patch, this is an unauthenticated, network-reachable deserialisation flaw that CISA says is already being exploited. Virtual CISO Services can help you map internet-facing Roller instances and decide which services should be reachable. Because active exploitation means abuse may already be underway, Managed Detection & Response gives you continuous detection and response for the next stage of an intrusion.

Affected and fixed versions

ProductAffectedFixed in
Apache Roller4.0.0 – < 6.1.56.1.5

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them.

Written with AI assistance from the sources above and checked automatically against them before publication.