Hackers Actively Exploit Critical Apache Roller RCE Flaw to Execute Code Without Authentication

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Hackers are actively exploiting a critical vulnerability in Apache Roller that lets them run code on affected servers without signing in, the Apache Software Foundation warned on November 17.

The flaw, tracked as CVE-2026-129448, affects versions 4.0.0 through 6.1.4 and carries a CVSS 3.1 score of 9.8 out of 10. Apache says administrators should upgrade to Roller 6.1.6 or later. Version 6.1.5 is also vulnerable, but Apache tracks it under a separate CVE.

Apache Roller is a Java-based blogging platform that can host multiple blogs and support teams of writers and editors. The vulnerability is in its XML-RPC endpoint, an interface that lets other software communicate with Roller.

The server accepts certain extended data types and rebuilds them into objects before checking whether the sender is allowed to use the service. That process, known as deserialization, is unsafe when the server reconstructs data supplied by an attacker.

The result is remote code execution, or RCE. An attacker who can reach the vulnerable service over the network can run code without a valid account or any action from a blog user.

Critical Apache Roller RCE Exploitation

Apache’s CVE record confirms active exploitation but does not identify the attackers, say how many systems have been targeted, or describe what attackers have done after gaining access.

The November disclosure expands the known affected range. Apache’s September advisory listed only version 6.1.5 under CVE-2026-82384.

The new record says the two CVEs describe the same underlying flaw across different releases. That matters for administrators who installed 6.1.5 to fix an earlier Apache Roller session vulnerability. That update fixed the session issue, not this code execution flaw.

Cyber Security News also covered active exploitation of a separate Apache Tomcat RCE flaw. The Roller issue is in the blogging application itself.

Apache Roller 6.1.6 turns off the affected extension types and rejects XML-RPC requests when the feature is turned off. On vulnerable releases, turning off XML-RPC in the administration interface is not enough.

Those versions can process incoming data before checking the setting, leaving the server exposed even when the dashboard shows the feature is disabled.

If an upgrade cannot happen immediately, Apache recommends setting enabledForExtensions to false in WEB-INF/web.xml or removing the /roller-services/xmlrpc servlet mapping. Both workarounds require a Roller restart.

Removing the mapping also takes the endpoint offline, so administrators should check whether any publishing tools depend on it before choosing that workaround. Neither option changes Apache’s recommendation to upgrade.

For teams managing several Roller deployments, first check the version running on each server rather than relying on the XML-RPC setting in the dashboard. Prioritize instances reachable from the internet, then verify that the fixed release is running after deployment.

Patching closes the flaw, but it doesn’t show whether a server was compromised before the update. Treat any suspected compromise as a separate investigation.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs

The post Hackers Actively Exploit Critical Apache Roller RCE Flaw to Execute Code Without Authentication appeared first on Cyber Security News.