Critical Apache Roller Flaw Under Active Exploitation
The Apache Software Foundation has released updates for a critical flaw in Apache Roller, the open-source Java blog server, and says the bug is being actively exploited. Tracked as CVE-2026-129448, it allows unauthenticated remote code execution through unsafe deserialization.
| Attribute | Value |
|---|---|
| Product | Apache Roller |
| CVE | CVE-2026-129448 |
| Type | Deserialization of untrusted data, leading to unauthenticated RCE |
| Affected versions | 4.0.0 through 6.1.4 (per Apache's advisory) |
| Fixed version | 6.1.6 or later |
| Exploitation | Actively exploited, per Apache |
| CVSS | Not stated in the source reporting (described as critical) |
Technical Details
Roller's XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. A remote attacker can therefore send a crafted request and run code on the server without credentials. A related issue, CVE-2026-82384, listed only 6.1.5 as affected, so check both advisories when auditing.
The reports do not say who is exploiting the flaw or how many servers have been compromised.
Mitigation
- Upgrade to Apache Roller 6.1.6 or later. This disables the extension types and rejects malicious XML-RPC requests.
- If you cannot upgrade immediately, set
enabledForExtensionstofalseinWEB-INF/web.xml, remove the/roller-services/xmlrpcservlet mapping, and restart Roller. - Do not rely on the admin-interface XML-RPC toggle. Older versions deserialize the request before checking that setting, so disabling it there does not protect you.
- Treat internet-facing Roller instances running affected versions as potentially compromised: review web server logs for requests to
/roller-services/xmlrpc, and check for unexpected processes or files.
