What changed
The vulnerable parser runs before the permission check
Apache disclosed CVE-2026-129448 on 17 November and says the issue is being actively exploited. Roller's XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. That can let a remote, unauthenticated attacker run code in affected installations. Apache has not provided a public count or attribution for the attacks.
The advisory says this is the same underlying flaw as CVE-2026-82384, which covered Roller 6.1.5. CVE-2026-129448 extends the affected range to versions 4.0.0 through 6.1.4. Taken together, those versions reach through 6.1.5; Apache recommends 6.1.6 or later.
The admin switch is not enough
Defender workflow
Check the endpoint that can still receive a request
- 1
Locate Roller. Find Roller installations and versions, including instances hosted behind a reverse proxy. Check whether
/roller-services/xmlrpcis reachable from untrusted networks. - 2
Upgrade or block the path. Move to Roller 6.1.6 or later. If that cannot happen immediately, Apache advises setting
enabledForExtensionstofalseinWEB-INF/web.xmlor removing the XML-RPC servlet mapping, then restarting Roller. - 3
Look back. Review requests to the XML-RPC endpoint, unusual Java process children and outbound connections from the Roller host. The vendor's exploitation statement justifies an investigation, but a request alone is not proof of successful code execution.
Defender note
A disabled feature can still have a live parser
This is a useful reminder to test where an application enforces an off switch. If the request body is parsed before the setting is checked, the risky work has already happened. Validate the actual route after mitigation instead of relying on the appearance of the administration screen.