Home/Research/Post

Apache Roller RCE Flaw CVE-2026-129448 Under Active Attack

Attackers are exploiting a critical Apache Roller flaw that allows unauthenticated remote code execution, prompting urgent security updates.

A critical vulnerability, tracked as CVE-2026-129448 (CVSS score of 9.8), in Apache Roller could allow an unauthenticated attacker to execute arbitrary code on a vulnerable server. Apache Roller is an open-source blogging platform written in Java. According to the Apache Software Foundation (ASF) the flaw is being actively exploited in attacks in the wild.

The issue affects Apache Roller versions 4.0.0 through 6.1.4. It stems from unsafe deserialization in the platform’s XML-RPC endpoint, which processes certain data before checking whether the requester is authenticated. An attacker doesn’t need valid credentials to reach this vulnerable code path.

“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.” reads the security notice published on the Apache mailing list. “This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected.”

The Apache project described the problem in its security notice published on the Apache mailing list:

The maintainers explained that the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This order of operations is the core security problem: the application processes attacker-controlled data before establishing whether the request should be trusted.

The ASF also confirmed that the vulnerability is the same issue previously tracked as CVE-2026-82384. That earlier advisory, published in September 2026, listed only Apache Roller 6.1.5 as affected. The new notice expands the affected version range to include releases from 4.0.0 through 6.1.4, making it important for administrators not to rely solely on the scope of the earlier advisory.

The project has explicitly confirmed exploitation in the wild, although it hasn’t disclosed technical details about the attacks, the threat actors involved, or the organizations being targeted.

“This issue is being actively exploited.” continues the notice.

Security researcher n0mi1k is credited with discovering the vulnerability, while Matt Raible reported it to the project. The ASF recommends upgrading to Apache Roller 6.1.6 or later. This release disables the vendor extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.

Organizations that can’t install the update immediately should apply one of the workarounds provided by the project. They can set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping. In either case, administrators must restart Apache Roller for the change to take effect.

The experts warn that simply disabling XML-RPC through the administration interface doesn’t fully address the problem in older releases. The vulnerable code can deserialize the request before checking that configuration setting, leaving the application exposed even when administrators believe they have turned the feature off.

The confirmed exploitation makes this more than a routine patching recommendation. Organizations running Apache Roller should identify every affected instance, check whether the XML-RPC endpoint is reachable, and prioritize the upgrade or the recommended workaround. Internet-facing systems deserve particular attention, but internal installations should not be overlooked: a server doesn’t need to be publicly accessible to become a useful target after an attacker gains access to an organization’s network.

The ASF has also warned that disabling the feature through the administration interface alone won’t protect older installations:

“Users who cannot upgrade right away should set “enabledForExtensions” to “false” in WEB-INF/web.xml, or remove the “/roller-services/xmlrpc” servlet mapping, and restart Roller.” concludes the advisory. “Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.”

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, Apache Roller)

Source: Security Affairs · 2026-11-18