Protect.Computer
NEWS

Apache Roller RCE Flaw CVE-2026-129448 Exploited in Attacks

· 1 min read · Got hacked Network safety
Apache Roller RCE Flaw CVE-2026-129448 Exploited in Attacks

Apache has warned that a critical flaw in Apache Roller, its open-source Java blogging server, is being exploited in the wild. The bug, CVE-2026-129448, lets an unauthenticated attacker run code on the server. BleepingComputer, quoting Apache’s advisory, says Roller’s XML-RPC endpoint accepts vendor extension types and deserializes them before it checks who is sending the request. Apache says it is the same vulnerability as CVE-2026-82384, which listed only Roller 6.1.5 as affected, and flags it as actively exploited.

Apache has not said who is behind the attacks or how many servers are compromised, according to BleepingComputer. BleepingComputer notes that Roller is a niche product with a much smaller market share than modern blogging platforms and CMSs.

How to check if you’re affected

Affected versions are, per the advisory text BleepingComputer quotes, Apache Roller 4.0.0 through 6.1.4; the same quote notes that the earlier CVE-2026-82384 listed 6.1.5. BleepingComputer reports that Apache’s fix is Roller 6.1.6 or later, which disables the extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature. The Apache Roller downloads page now lists 6.1.7 as the current “best available” release and asks you to read its release notes, including behavior changes, before upgrading a live site.

If you cannot upgrade right away, BleepingComputer relays Apache’s temporary mitigation:

  • In WEB-INF/web.xml, set enabledForExtensions to false.
  • Remove the /roller-services/xmlrpc servlet mapping.
  • Restart Roller.

Apache says that switching XML-RPC off in the administration interface is not enough, because older versions deserialize the request before checking that setting.

Apache’s advisory thread did not render for us, so the advisory wording above comes through BleepingComputer. Checking a server you suspect was hit for unexpected files or processes is our suggestion; none of the sources give indicators of compromise.

Sources

Related reading