- Apache says the flaw in Roller 4.0.0 through 6.1.4, CVE-2026-129448, is being actively exploited. It is rated 9.8 and lets an unauthenticated attacker run code.
- Turning off XML-RPC in the administration screen does not protect these versions, because they process the request before checking that setting.
- Apache recommends Roller 6.1.6 or later. Teams that cannot upgrade yet can edit web.xml and restart.
A setting that says "off" is a promise. In Apache Roller 4.0.0 through 6.1.4, that promise does not hold for XML-RPC. An administrator who switched the feature off in the interface may think the exposure is closed. Apache says it is not.
What Apache has said
The Apache Software Foundation published an advisory for CVE-2026-129448. It scores the flaw 9.8 out of 10 on the CVSS 3.1 scale. It covers Roller 4.0.0 through 6.1.4. Apache says an unauthenticated remote attacker can use it to run arbitrary code.
Apache says the flaw "is being actively exploited." It gives no detail. BleepingComputer reports that Apache has not said who is behind the attacks or how many servers are affected. The advisory credits n0mi1k as the finder and Matt Raible as the reporter.
How the flaw works
Roller is a blogging server for groups, written in Java and released as open source. It has an XML-RPC endpoint, which is a web address where other software can send it instructions.
Apache says this endpoint accepts "vendor extension types". It rebuilds them into program objects before it checks who is asking. That rebuilding step is called deserialization.
Here is why that matters in general. When a program rebuilds objects from incoming data, the sender can influence which objects get built. Building some objects runs code as a side effect. So attacker-chosen data can start code running.
A login check placed after that step comes too late. The risky work is already done by the time the check runs.
Why the admin switch misleads
Apache says that disabling XML-RPC in the administration interface is not enough. Older versions rebuild the request first. Only then do they look at whether the setting is on.
The lesson here is that a control only counts if it runs before the risky work. The switch looks like a lock. Apache says the dangerous step happens before the lock is consulted.
The advisory does not say whether the interface warns administrators about this gap. Until that is clear, a switch that reads "off" is not proof that the endpoint is closed.
A version record that needs a second look
Apache says CVE-2026-129448 and CVE-2026-82384 describe one flaw. The earlier record listed only 6.1.5 as affected. A team relying on it alone would miss 4.0.0 through 6.1.4.
Apache recommends 6.1.6 or later. Check the installed version against the new advisory, not a single CVE entry.
A small product is still an exposure
BleepingComputer says Roller's market share is much smaller than that of modern CMS platforms. That says nothing about which organisations run it. It also says nothing about how closely anyone watches those servers.
For context, BleepingComputer counts 41 Apache flaws added to CISA's known-exploited list since November 2021. It says ransomware groups also used eight of them. Those figures cover Apache products in general, not Roller.
What to do and what to ask
Apache recommends upgrading to Roller 6.1.6 or later. That release turns the extension types off. It also refuses XML-RPC requests whenever XML-RPC is disabled.
Teams that cannot upgrade right away have two options from Apache. They can set "enabledForExtensions" to "false" in WEB-INF/web.xml. Or they can remove the "/roller-services/xmlrpc" servlet mapping. Either way, Roller must be restarted.
Leaders can put four questions to their teams. Do we run Roller anywhere, including old blogs and internal sites? Which version is each one? Can the XML-RPC path be reached from outside our network? If a server was exposed, how would we check whether it was already compromised?
Apache has published no details on the attacks, so the last question has no ready answer. Confirm the real state of each server rather than trusting the setting.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Apache Software Foundation.





