SAASMENT

News

Attackers are running code on Apache Roller without a login.

Apache says an XML-RPC deserialization flaw in Roller 4.0.0 through 6.1.4 is already being exploited, and turning XML-RPC off in the admin screen does not stop it.

Illustration of an unauthenticated request cracking a blog server through an open port

Impact

What was impacted
Apache Roller 4.0.0 through 6.1.4. The XML-RPC endpoint accepts vendor extension types and deserializes them before it authenticates the caller (CVE-2026-129448, CVSS 9.8), which can lead to remote code execution. Apache says this is the same issue as CVE-2026-82384 (CVSS 9.8), patched in September 2026 under an advisory that listed only Roller 6.1.5 as affected.
Who was impacted
Operators of Apache Roller blogs in that version range, especially where /roller-services/xmlrpc is reachable. Apache says the flaw is being exploited and did not name targets or describe the exploit.
What you need to do
Upgrade to Apache Roller 6.1.6 or later. That release disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. If you cannot upgrade now, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. Do not rely on disabling XML-RPC in the administration UI.

The Apache Software Foundation says Apache Roller, the open-source Java blogging platform, is under active attack. CVE-2026-129448 (CVSS 9.8) is unauthenticated deserialization in the XML-RPC endpoint. The endpoint accepts vendor extension types and deserializes them before it checks who sent the request, so a remote attacker with no account can run code. Apache did not describe the exploit or name who is being targeted.

The same flaw was tracked earlier as CVE-2026-82384, also scored 9.8. That issue was patched in September 2026, and the advisory listed only Apache Roller 6.1.5 as affected. The new record covers versions 4.0.0 through 6.1.4. Researcher n0mi1k is credited with finding the flaw, and Matt Raible with reporting it.

The fix is Apache Roller 6.1.6 or later. That version disables the extension types and rejects XML-RPC requests when the XML-RPC feature is turned off.

If an upgrade has to wait, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. Apache says turning XML-RPC off in the administration UI is not enough. Older versions deserialize the request before they consult that setting.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to active exploitation of Apache Roller CVE-2026-129448 (CVSS 9.8). Apache Roller 4.0.0 through 6.1.4 deserializes vendor extension types on the XML-RPC endpoint before authenticating the requester, so an unauthenticated remote attacker can run code. Apache says this is the same issue as CVE-2026-82384 (CVSS 9.8), which was patched in September 2026 under an advisory that listed only Roller 6.1.5 as affected. The new advisory covers 4.0.0 through 6.1.4. Apache confirmed active exploitation and did not describe the exploit or name targets. The credited finder is n0mi1k; Matt Raible reported it.

Context:
- What was impacted: the Apache Roller XML-RPC endpoint (/roller-services/xmlrpc) on versions 4.0.0 through 6.1.4.
- Who should care: anyone running those Roller versions, especially if the XML-RPC path is reachable from the network.
- What to do: upgrade to Apache Roller 6.1.6 or later. If you cannot upgrade immediately, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart. Disabling XML-RPC in the administration UI does not stop the deserialization on older versions.

Do this in order. Ask before editing web.xml, restarting Roller, or taking a site offline. Prefer read-only inventory first. Do not write or run an exploit, a deserialization payload, or a proof of concept.

1. Inventory
   - Find Apache Roller installs and record the version. Flag anything from 4.0.0 through 6.1.4.
   - Note whether /roller-services/xmlrpc is exposed, and whether XML-RPC is only switched off in the admin UI.
2. Contain
   - If a vulnerable instance is reachable and cannot be upgraded today, propose one of the two Apache workarounds: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping. Restart only after I approve it.
   - Do not treat an admin-UI disable as containment.
3. Remediate
   - Plan the upgrade to Apache Roller 6.1.6 or later, then restart so the new build is what is running.
   - On a host that may already have been hit, look for unexpected processes and web shells under the Roller account before calling the upgrade complete. Ask before deleting files.
4. Verify
   - Confirm the running version is 6.1.6 or later, or that the chosen workaround is in the deployed web.xml and the service was restarted.
5. Report back
   - Versions found, whether XML-RPC was internet-facing, upgrade or workaround applied, signs of compromise, and anything still on 6.1.4 or older.

Do not invent indicators, victim names, or version numbers beyond what I provided. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform