CVE-2026-129448: Apache Roller RCE exploited in attacks

Apache has warned that a critical flaw in its Roller blogging platform is being actively exploited in the wild, and has urged administrators to patch immediately. The vulnerability, tracked as CVE-2026-129448, carries a CVSS severity score of 9.8 out of 10 and allows an unauthenticated attacker to run arbitrary code on a vulnerable server.
Apache Roller is an open-source, Java-based group-blogging server. It is a niche product with a much smaller market share than modern content management systems, but the flaw is severe because it needs no login and no user interaction: a single crafted request to the platform's XML-RPC endpoint is enough.
Deserialization before authentication
According to Apache's security advisory, published on Tuesday 17 November, the flaw is a case of deserialization of untrusted data. "Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester," the advisory states.
The endpoint in question is /roller-services/xmlrpc, which exposes the old Blogger and MetaWeblog publishing interfaces. Because the XML-RPC library is configured to accept vendor extension types, an attacker can send a request containing a base64-encoded Java serialized object, which the library rebuilds before Roller ever checks credentials or whether XML-RPC is switched on.
A patch bypass, not a new bug
Apache says the flaw is the same vulnerability previously tracked as CVE-2026-82384, which was patched in September 2026. That earlier advisory listed only Apache Roller 6.1.5 as affected, but the new advisory expands the vulnerable range to every release from 4.0.0 through 6.1.4. In effect, the September fix did not close the deserialization path for all configurations, so anyone who upgraded to 6.1.5 and closed the ticket needs to reopen it. Security researcher n0mi1k is credited with finding the flaw, and Matt Raible with reporting it.
Apache has confirmed the flaw is being exploited, but has not shared details of the attacks, the threat actors involved, or how many servers have been compromised. No public set of indicators of compromise has been released alongside the advisory.
What administrators should do
Roller users should upgrade to Apache Roller 6.1.6 or later, which disables the vendor extension types and rejects XML-RPC requests when the XML-RPC feature is switched off. Administrators who cannot upgrade immediately can apply a temporary mitigation by setting "enabledForExtensions" to "false" in WEB-INF/web.xml, or by removing the "/roller-services/xmlrpc" servlet mapping, and then restarting Roller.
Apache stresses that switching XML-RPC off in the administration interface alone is not enough to block attacks, because older versions deserialize the request before they ever consult that setting. Any Roller deployment with the XML-RPC endpoint reachable from the internet should be checked for compromise before it is patched over.
The incident is the latest in a long run of Apache flaws abused in the wild. Earlier this month Apache fixed a critical vulnerability in the HTTP/2 module of Apache HTTP Server that could also allow unauthenticated remote code execution, and since November 2021 the US Cybersecurity and Infrastructure Security Agency has added 41 Apache flaws to its catalogue of vulnerabilities exploited in the wild, eight of them also abused by ransomware gangs.
Sources: BleepingComputer; The Hacker News.