RC RANDOM CHAOS

Apache Roller deserializes XML-RPC before authenticating

Apache Roller 6.1.6 patches CVE-2026-129448, an unauthenticated XML-RPC deserialization RCE being exploited in the wild. Upgrade and mitigation details.

· 2 min read
Apache Roller deserializes XML-RPC before authenticating

Apache Roller’s XML-RPC endpoint deserializes vendor extension types out of a request before it authenticates whoever sent it. That ordering is the bug. CVE-2026-129448 lets an unauthenticated remote attacker drop a crafted XML-RPC payload onto a vulnerable server and run arbitrary code, and Apache’s Tuesday advisory says it is already being exploited.

Roller is an open-source, Java-based group-blogging server with a small footprint next to WordPress or Ghost. The niche status does not help much here. Any instance running versions 4.0.0 through 6.1.4 and exposing the /roller-services/xmlrpc servlet is reachable, and Java deserialization of attacker-controlled data is one of the most reliable paths to code execution there is: feed the right gadget chain into a readObject call and the host does the work. Running that deserialization before the auth check means the attacker never needs a credential.

Apache notes this is the same flaw as CVE-2026-82384, which had been filed against only Roller 6.1.5. The new identifier widens the affected range back to 4.0.0 and attaches the active-exploitation flag. If you tracked the earlier CVE and decided an older release left you clear, check again.

The fix is Roller 6.1.6 or later, which disables the extension types and rejects the malicious XML-RPC requests after turning the XML-RPC feature off.

If you can’t upgrade immediately, the manual mitigation is to edit WEB-INF/web.xml: set enabledForExtensions to false, remove the /roller-services/xmlrpc servlet mapping, and restart Roller. One detail matters here. Switching XML-RPC off in the admin UI does not close the hole, because older versions deserialize the request before they check whether that setting is on. The dangerous code runs regardless of the toggle, so the mitigation has to happen in web.xml, not in the running application’s settings.

Apache has not said who is behind the attacks or how many servers are already compromised.

The Roller advisory lands in a busy stretch for Apache software under active attack. In April, CISA flagged a 13-year-old Apache ActiveMQ bug (CVE-2026-34197) as exploited and gave federal agencies two weeks to patch. Earlier this month Apache fixed an unauthenticated RCE in the HTTP/2 module of Apache HTTP Server. Since November 2021, CISA has added 41 Apache flaws to its Known Exploited Vulnerabilities catalog, eight of them also used by ransomware crews.

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.