Attackers are exploiting a critical Apache Roller flaw to run code on vulnerable blogging servers without signing in. In a November 17 advisory, Apache urged administrators to upgrade to Roller 6.1.6 or later, even if they have already switched off the affected feature in the administration panel.

Two advisories cover the same flaw

Roller is an open-source blogging platform that uses Java and lets multiple authors publish to a shared site. It has a smaller footprint than many modern publishing platforms, but Apache has confirmed that attackers are exploiting the vulnerability. The project has yet to identify who carried out the attacks or say how many servers they compromised.

The latest advisory changes which releases administrators need to check. An earlier notice, CVE-2026-82384, listed only Roller 6.1.5. The new notice, CVE-2026-129448, covers versions 4.0.0 through 6.1.4. Apache says both identifiers describe the same defect, so administrators running any release from 4.0.0 through 6.1.5 should take action.

Why the administration setting leaves servers exposed

The Apache Roller flaw affects XML-RPC, an interface that allows external software to send requests to the blogging platform. Older releases process certain incoming data before they check the sender’s credentials. They also perform that work before they check whether an administrator has turned off XML-RPC.

That sequence explains why the dashboard setting offers insufficient protection. An administrator can switch off XML-RPC and see the feature listed as inactive, yet Roller can still process a request far enough for an attacker to run code. Operators who previously disabled the interface through the dashboard therefore still need to review their installations.

Roller 6.1.6 closes the gap

Roller 6.1.6 disables the XML-RPC extension types involved in the attacks. It also rejects malicious requests when an administrator has turned off XML-RPC. Apache recommends an immediate upgrade to this release or a later version.

For teams that need time to schedule the update, Apache provides a temporary workaround. Administrators should set enabledForExtensions to false in WEB-INF/web.xml, remove the /roller-services/xmlrpc servlet mapping, and restart Roller so the changes take effect.


0 responses to “Apache Roller flaw lets attackers run code on servers”