Apache Roller CVE-2026-129448: Exploited Pre-Auth XML-RPC Deserialization RCE Back to 4.0.0
Introduction
Apache Roller's developers warned on November 17 that CVE-2026-129448, an unauthenticated CVSS 9.8 deserialization RCE in the blog server's XML-RPC endpoint, is being actively exploited. The new CVE widens an earlier record, CVE-2026-82384, that only listed 6.1.5. In fact every release from 4.0.0 onward is affected, and a public PoC has existed since September. Turning XML-RPC off in the admin UI does not help. Upgrade to 6.1.7, or block /roller-services/xmlrpc at the proxy today.
What Happened
Roller's XML-RPC servlet, which supports the MetaWeblog and Blogger APIs used by desktop blogging clients, ran with vendor extensions enabled. That let it deserialize attacker-supplied Java objects before authenticating the requester, and before checking whether XML-RPC was even turned on (CWE-502 plus CWE-306).
| Date (2026) | Event |
|---|---|
| Sep 25 | CVE-2026-82384 published, listing only Roller 6.1.5 as affected |
| Sep 28 | Public proof-of-concept repository created on GitHub |
| Nov 11 | Roller 6.1.7 released |
| Nov 17 | Apache publishes CVE-2026-129448 on oss-security: same bug, affected range 4.0.0–6.1.4 (6.1.5 already covered), actively exploited |
Credit goes to n0mi1k (finder) and Matt Raible (reporter). Apache has not published attacker IPs or payload details, and as of November 17 the CVE was not in CISA KEV.
The fix landed in 6.1.6, which disables extension types and rejects XML-RPC requests when the feature is turned off. 6.1.7 is the current recommended release. Apache's header text says "releases before 6.1.5", which contradicts the 6.1.6 fix. Go by the fixed release, not the header.
Why It Matters
Roller is not a household name, but it runs long-lived corporate, university and government blogs, and many of those were installed years ago and are rarely looked at. A deserialization bug in a Tomcat-hosted Java app gives code execution as the Tomcat user. From there an attacker can drop JSP webshells into webapps/, read database credentials from roller-custom.properties, and pivot to whatever the app server can reach.
The two-CVE history is the trap here. Anyone who read the September record saw "6.1.5 only" and concluded that older installs were fine. They were not, and the PoC has been public for seven weeks.
Who Is Affected
- Apache Roller 4.0.0 through 6.1.5, per the combined CVE-2026-129448 and CVE-2026-82384 records.
- Fixed: 6.1.6. Recommended: 6.1.7.
- Exposed path:
/roller-services/xmlrpc, or/roller/roller-services/xmlrpcwhen Roller is not the root context. - Installs where XML-RPC is disabled in the admin UI are still vulnerable on older versions.
- Dependency scanners that read
pom.xmlmay miss Roller, because it is usually deployed as a downloaded WAR.
How to Protect Yourself
1. Find the version you are running
# Roller WARs and exploded deployments
find / -xdev \( -iname 'roller*.war' -o -path '*/webapps/roller*/WEB-INF' \) 2>/dev/null
# version from the deployed jar names / manifest
find / -xdev -path '*WEB-INF/lib/roller-*.jar' 2>/dev/null
unzip -p /path/to/roller.war META-INF/MANIFEST.MF 2>/dev/null | grep -i version
2. Upgrade to 6.1.7
Back up the database and roller-custom.properties, deploy the 6.1.7 WAR, and restart Tomcat. Upgrade notes are in the Roller release page.
3. If you can't upgrade today, close the endpoint
Apache's interim options are to set enabledForExtensions to false in WEB-INF/web.xml, or to remove the /roller-services/xmlrpc servlet mapping, then restart. Blocking the path at the edge works too, unless you rely on a desktop blogging client:
# nginx in front of Tomcat
location ~* /roller-services/xmlrpc { return 403; }
# Apache httpd
<LocationMatch "/roller-services/xmlrpc">
Require all denied
</LocationMatch>
4. Hunt the logs
Look for POSTs to the endpoint, especially from clients with no history of XML-RPC use or with unusually large bodies. If your WAF or proxy logs request bodies, search for the serialization markers the Corgea write-up cites: ex:serializable, the extensions namespace, and rO0AB, the Base64 Java serialization header.
sudo zgrep -hE 'POST [^ ]*/roller-services/xmlrpc' /var/log/nginx/access.log* /var/log/apache2/access.log* /opt/tomcat/logs/localhost_access_log* 2>/dev/null | awk '{print $1}' | sort | uniq -c | sort -rn | head
# body-logging WAFs
sudo zgrep -lE 'ex:serializable|rO0AB' /var/log/modsec_audit.log* 2>/dev/null
5. Check the host for webshells and child processes
# new JSPs in Tomcat webapps
find /opt/tomcat*/webapps /var/lib/tomcat*/webapps -name '*.jsp' -newermt '2026-09-28' 2>/dev/null
# Tomcat JVM spawning shells or downloaders
ps -eo pid,ppid,user,cmd --forest | grep -A2 '[c]atalina' | grep -E 'bash|sh -c|curl|wget|python|nc '
In the Roller admin UI, also look for unknown admin users and recently changed themes or templates.
6. If it was exposed, assume compromise
If the endpoint was internet-facing on a vulnerable version, preserve logs and a disk snapshot first, then rebuild from a clean image rather than cleaning in place. Rotate the database password, mail credentials and anything else stored in roller-custom.properties or reachable by the Tomcat user.