Skip to content
feed: live
0dayNews
apache
● Breaking

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

Apache says a Roller XML-RPC deserialization flaw is under active exploitation. Upgrade to 6.1.6 or later; turning XML-RPC off in the admin UI is not enough.

Apache Roller RCE CVE-2026-129448 Is Exploited in Attacks
Image: AI-generated — conceptual illustration, not incident evidence / 0dayNews AI Cover · Generated on-site infrastructure — no external license
kilobaudDave "Kilobaud" Ferris·Published ·2 min read

Apache has flagged a critical Roller flaw, CVE-2026-129448, as actively exploited, according to BleepingComputer’s report on its Tuesday advisory. Roller is a niche product, a Java group-blogging server, but niche has never meant unattended, and an unauthenticated code execution bug in an internet-facing blog is worth an afternoon.

What Apache says

The advisory describes deserialization of untrusted data in Apache Roller versions 4.0.0 through 6.1.4. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester, so an unauthenticated remote attacker can execute arbitrary code. Apache adds that this is the same vulnerability as CVE-2026-82384, which listed only Roller 6.1.5 as affected, and that this issue is being actively exploited.

Apache has not said who is behind the attacks or how many servers have been compromised. We are not going to guess at either.

What to do

  • Upgrade to Apache Roller 6.1.6 or later. Per Apache, that release disables the extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature.
  • If you cannot upgrade yet, Apache’s temporary mitigation is to set “enabledForExtensions” to “false” in WEB-INF/web.xml, remove the “/roller-services/xmlrpc” servlet mapping, and restart Roller.
  • Do not rely on the administration UI toggle. Apache states that disabling XML-RPC there is not enough, because older versions deserialize the request before checking whether the setting is on.

Why this one keeps coming back

The version range is the interesting part. The earlier record for this bug named only 6.1.5, and the new advisory stretches the affected range back to 4.0.0. Readers who patched on the September notice and assumed they had closed it should check their version against the wider range. We covered the original fix in Apache Roller Patches Critical XML-RPC Deserialization Bug, and the earlier record is at CVE-2026-82384.

Analysis: a record that under-reports the affected versions tends to leave the older installs unpatched, and older installs are what a small project like Roller has plenty of. That is a pattern, not a finding about these attacks.

The wider Apache picture is busy. Earlier this month Apache also fixed a critical flaw in the HTTP/2 module of its web server, which we covered in Apache HTTP Server mod_http2 CVE-2026-119618 RCE. More on the Apache hub.

Found this useful? Share it.