Apache has issued an urgent warning for administrators running Apache Roller after confirming that attackers are actively exploiting a critical remote code execution flaw. The vulnerability, tracked as CVE-2026-129448, affects Roller versions 4.0.0 through 6.1.4 and allows an unauthenticated attacker to execute arbitrary code on a vulnerable server. Apache has released Roller 6.1.6 to address the issue, and organizations that cannot update immediately are being urged to apply temporary mitigation steps.
The flaw affects Apache Roller, an open-source, Java-based group-blogging server. Although it has a smaller user base than mainstream content-management systems, the issue is serious because it can give attackers full control over affected servers. The vulnerability involves the deserialization of untrusted data through the platform’s XML-RPC endpoint.
Roller accepts vendor extension types and deserializes them before authenticating the requester, allowing an attacker to send malicious data that the server processes before checking whether the sender is authorized. This unsafe sequence can lead to arbitrary code execution, enabling attackers to run commands, install malware, steal data, or use the compromised server for further attacks.
Apache has confirmed that CVE-2026-129448 is being exploited in the wild, although it has not disclosed details about the attackers, the scale of the campaign, or how many systems have already been compromised. The company also noted that the flaw is the same underlying issue as CVE-2026-82384, which had previously listed only Apache Roller 6.1.5 as affected. The confirmation of active exploitation raises the urgency considerably. Organizations running Roller should assume that internet-facing instances may be targeted and should prioritize patching over routine maintenance.
The most effective response is to upgrade to Apache Roller 6.1.6 or later. The updated release disables the vulnerable extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature, closing the path attackers are using to exploit the flaw. Administrators who cannot upgrade immediately can reduce exposure by setting enabledForExtensions to false in WEB-INF/web.xml, removing the /roller-services/xmlrpc servlet mapping, and restarting Roller. These steps block the vulnerable functionality while a permanent update is prepared.
Apache specifically warns that disabling XML-RPC through the administration interface is not enough on older versions, because affected Roller builds deserialize incoming requests before checking whether the XML-RPC setting has been turned off. This means an administrator may believe the service is disabled while the server remains exploitable.
The Roller flaw arrives amid a broader run of Apache security issues, including a recent critical vulnerability in the HTTP/2 module of Apache HTTP Server that could also allow unauthenticated attackers to achieve remote code execution. Since November 2021, CISA has added 41 Apache flaws to its catalog of vulnerabilities exploited in the wild, and eight of those have also been abused by ransomware gangs. Organizations should inventory their systems, identify any Roller installations, and treat this vulnerability as an immediate security priority.
Read the original article:
Apache Roller RCE Vulnerability Actively Exploited in Attacks
