← All articles

Apache Roller vulnerability allows unauthenticated code execution

Apache Roller vulnerability allows unauthenticated code execution

The Apache Roller vulnerability CVE-2026-129448 is being actively exploited, the Apache Software Foundation (ASF) says. Apache Roller is an open-source, Java-based blogging platform. The flaw has a CVSS score of 9.8, the highest criticality range, and can allow an attacker to run code on a vulnerable system without logging in.

The problem is unauthenticated deserialization in Roller’s XML-RPC endpoint. Deserialization is the process of turning received data into usable software objects. XML-RPC is a way for applications to exchange commands and information using XML. In affected Roller versions, the endpoint accepts vendor extension types and processes them before checking whether the requester is authenticated.

That order is the central security issue. A remote attacker can send specially prepared data to the XML-RPC endpoint, and Roller may process it before confirming the requester’s identity. The project maintainers describe the result as arbitrary code execution, meaning the attacker may be able to make the server run commands of their choice.

The affected range identified by ASF covers Apache Roller versions 4.0.0 through 6.1.4. ASF also says CVE-2026-129448 is the same issue as CVE-2026-82384, which was patched in September 2026 and had listed only Apache Roller 6.1.5 as affected. The advisory therefore links the newly tracked vulnerability to the earlier disclosure and to the broader version range now identified by the maintainers.

ASF has confirmed that exploitation is taking place in the wild, but it has not disclosed how the attacks are being carried out or which organisations or systems are being targeted. That means administrators should treat exposed Roller installations as at risk even though the available information does not identify a particular attacker or campaign.

The recommended fix is to upgrade to Apache Roller 6.1.6 or later. That release disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. The project credits security researcher n0mi1k with finding the flaw and acknowledges Matt Raible for reporting it.

If an immediate upgrade is not possible, administrators can set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and then restart Roller. A servlet mapping connects a web request path to a server component that handles it. These changes address the endpoint at the configuration or deployment level.

ASF specifically warns that disabling XML-RPC in Roller’s administration interface is not sufficient on older versions. Those versions deserialize the request before checking that administrative setting, so the dangerous processing can occur even when the feature appears disabled in the interface. For organisations reviewing their exposure, AEU-I offers security-first IT, infrastructure and consulting relevant to planning these upgrade and mitigation steps.

Website owners and IT teams should identify every Apache Roller installation, check its version, and prioritise systems reachable from the internet. Because exploitation is confirmed and authentication is not required, leaving an affected installation unchanged carries a direct risk of remote code execution.

Also available in: DeutschItalianoShqip