CriticalVulnerabilityActive

Apache says Roller RCE flaw CVE-2026-129448 is exploited in attacks

Apache says Roller 4.0.0 through 6.1.4 has an unauthenticated RCE flaw exploited in attacks; BleepingComputer reports upgrading to 6.1.6.

Published
Fixed in
Apache Roller 6.1.6 or later
Exploitation
Yes, according to Apache as reported by BleepingComputer; Apache has not published details of the attacks

Live scores

CVE-2026-82384
EPSS
0.010
low predicted chance of attack
VEDAS
0.051
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet

What happened

According to BleepingComputer, Apache has released security updates for a critical Apache Roller flaw tracked as CVE-2026-129448. BleepingComputer reports that Apache has flagged the flaw as actively exploited in the wild. Roller is an open-source, Java-based group-blogging server.

BleepingComputer quotes Apache’s Tuesday advisory as saying that deserialization of untrusted data in Roller 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The advisory says the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. It also says this is the same vulnerability as CVE-2026-82384, which listed only Roller 6.1.5 as affected.

What is not confirmed: according to BleepingComputer, Apache has not provided details about the attacks, including who is responsible or how many servers have been compromised. We have not independently verified the exploitation claim, and this advisory rests on a single outlet’s report of Apache’s advisory.

Am I affected?

Per the advisory as quoted by BleepingComputer, Apache Roller 4.0.0 through 6.1.4 is affected. Because the earlier CVE-2026-82384 listed 6.1.5, treat 6.1.5 as in scope too until you confirm against Apache’s advisory; the fix BleepingComputer cites is 6.1.6 or later.

BleepingComputer quotes Apache as saying that turning off XML-RPC in the administration user interface is not enough. Older versions deserialize the request before checking whether that setting is on.

Whether a given server has been targeted or compromised: not confirmed in the sources.

What to do now

  1. Upgrade to Apache Roller 6.1.6 or later. According to BleepingComputer, this release disables the extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature.
  2. If you cannot upgrade immediately, BleepingComputer reports Apache’s temporary mitigation: set “enabledForExtensions” to “false” in WEB-INF/web.xml, remove the “/roller-services/xmlrpc” servlet mapping, and restart Roller.
  3. Do not rely on switching off XML-RPC in the admin UI alone, since Apache says older versions deserialize the request first.
  4. Read Apache’s own advisory for CVE-2026-129448 directly; the sources provided here do not include its URL, so it is not linked.

Sources