Threat Intelligence

Apache Roller Flaw Lets Attackers Run Code Without a Login, and It Is Already Being Exploited

The Hacker News · 19 Nov 2026
Key Takeaway If your business runs Apache Roller, upgrade to 6.1.6 or later straight away, because attackers are already exploiting this flaw and no login is needed.

The Apache Software Foundation (ASF) has warned that a critical vulnerability in Apache Roller, an open-source, Java-based blogging platform, is being actively exploited in the wild. The flaw is tracked as CVE-2026-129448 and carries a severity score of 9.8 out of 10.

The problem sits in Roller's XML-RPC endpoint. According to the project maintainers, the endpoint accepts vendor extension types and deserializes them before it checks who is making the request. Deserialization of untrusted data means the software rebuilds objects from input it should not trust, and here it lets an unauthenticated remote attacker execute arbitrary code. Versions 4.0.0 through 6.1.4 are affected.

ASF also noted that the issue is the same as CVE-2026-82384, which was patched in September 2026 and listed only Apache Roller 6.1.5 as affected. ASF did not share details of how the flaw is being exploited or who is being targeted. The flaw was found by a researcher named n0mi1k and reported by Matt Raible.

Users are advised to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is turned off. If patching cannot happen immediately, ASF recommends setting "enabledForExtensions" to "false" in WEB-INF/web.xml, or removing the "/roller-services/xmlrpc" servlet mapping, and then restarting Roller. ASF warns that switching off XML-RPC in the administration screen is not enough, because older versions process the request before checking that setting.

Why it matters

Many teams would treat the administration setting that disables XML-RPC as a sufficient mitigation, but ASF says older versions deserialize the request before checking it, so that assumption fails and exposed servers stay vulnerable. Anyone running Roller 4.0.0 through 6.1.4 with the XML-RPC endpoint reachable is exposed to attackers who need no credentials. Because the flaw overlaps with one patched in September 2026, teams that considered this issue closed need to confirm which version they actually run.

What to do

  • Upgrade Apache Roller to version 6.1.6 or later.
  • Set "enabledForExtensions" to "false" in WEB-INF/web.xml if you cannot patch immediately, then restart Roller.
  • Remove the "/roller-services/xmlrpc" servlet mapping as an alternative stopgap, then restart Roller.
  • Do not rely on disabling XML-RPC in the administration UI, as older versions still process requests first.
Apache Roller RCE CVE-2026-129448 Deserialization Active Exploitation

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.