Apache warns attackers are exploiting a critical flaw in Roller blog servers
The Apache Software Foundation says CVE-2026-129448, a 9.8-rated flaw in the Roller blog server's XML-RPC endpoint, is being actively exploited. Roller 4.0.0 through 6.1.4 is affected; 6.1.6 fixes it.
Warden, covering security, outages and the rules for tech
, 2 min read
9.8CVSS score of CVE-2026-129448 (out of 10)
What to know
- CVE-2026-129448 lets an attacker who has not logged in run code on an Apache Roller server through its XML-RPC endpoint.
- Apache says the flaw is being actively exploited; it has not said by whom or how many servers were hit.
- Roller 4.0.0 through 6.1.4 is affected and 6.1.6 or later fixes it; turning off XML-RPC in the admin panel does not block the attack.
The Apache Software Foundation has warned that attackers are exploiting CVE-2026-129448, a critical flaw in Apache Roller, the open-source Java blog server. In an advisory on November 17, Apache said "this issue is being actively exploited," according to Daily CyberSecurity, which quoted the advisory. Apache has not named the attackers or said how many servers were compromised.
The flaw is rated 9.8 out of 10 on the CVSS scale and lets an attacker who has not logged in run code on the server. It affects Roller 4.0.0 through 6.1.4. Version 6.1.6 or later fixes it.
What the flaw is
Roller has an XML-RPC endpoint that lets desktop blogging tools post to a blog remotely. According to Daily CyberSecurity and the security news service Mallory, that endpoint accepts vendor "extension" data types and turns them back into Java objects before it checks who sent the request. Unsafe deserialization of this kind is a common route to remote code execution: a crafted request makes the server build objects that run the attacker's commands.
Apache had already disclosed the same bug in September as CVE-2026-82384, when it released Roller 6.1.6. That earlier record listed only version 6.1.5 as affected. The new CVE widens the range back to 4.0.0, which means many older Roller installs that were assumed safe were exposed. Daily CyberSecurity credits a researcher known as n0mi1k with finding the flaw.
The fix in 6.1.6 turns off the extension types and rejects XML-RPC requests when the feature is disabled.
A setting that does not help
Both reports stress one trap: switching off XML-RPC in Roller's admin panel does not stop the attack on older versions, because the request is deserialized before that setting is checked.
For servers that cannot be upgraded right away, Apache's suggested workarounds, as reported by Daily CyberSecurity, are to set enabledForExtensions to false in the WEB-INF/web.xml file, or to remove the /roller-services/xmlrpc servlet mapping, and then restart Roller. Administrators should also check server logs for unusual XML-RPC requests, since a server patched today may already have been hit.
As of November 17 the flaw was not in the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog, per Daily CyberSecurity. Our guide on how to read a security advisory explains what "actively exploited" and the CVSS score mean in practice, and our CVSS explainer covers how the 9.8 is calculated.
Why it matters
Roller is a small project, but blog servers sit on the open internet by design, and this flaw needs no password, so any unpatched install is a ready entry point into the network behind it. It follows attacks on an Apache Axis bug in Confluence Data Center and the disclosure of the Java4Shell runtime flaw, both in Java server software. Anyone running Roller should upgrade to 6.1.6 or later, or apply the workaround, and check for signs of compromise, as with any zero-day that is already in use.
Sources
- CVE-2026-129448: Apache Roller RCE Actively Exploited, Patch Now, Daily CyberSecurity, November 17, 2026
- Apache Warns of Active Exploitation of Critical Roller XML-RPC RCE Flaw, Mallory, November 17, 2026
Internet, outages and security
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.