Apache reports active exploitation of a code-execution flaw in Roller, its Java-based blogging server. The new advisory extends the known affected range to 4.0.0 through 6.1.4 under CVE-2026-129448. The same defect was previously documented for 6.1.5 as CVE-2026-82384.
Upgrade to the current Roller release. Turning XML-RPC off in the administration screen is insufficient on affected versions. XML-RPC, an interface for remote application calls, parses the dangerous data before checking that setting or authenticating the caller.
One defect, a broader affected range
Arnout Engelen’s November 17 advisory identifies unsafe deserialization, converting incoming data into program objects. The XML-RPC endpoint accepts extension types that can trigger code execution while the request is being parsed. An attacker who can reach that endpoint needs no account or user interaction.
Apache’s earlier CVE record names Roller 6.1.5 and explains that the servlet remains mapped even when XML-RPC is disabled globally. The new record covers 4.0.0 through 6.1.4 and explicitly says this is the same vulnerability.
The November warning therefore expands exposure and adds an exploitation report. It does not describe a new bypass of the September repair. Apache’s security page records 6.1.6, released September 24, as the fix for the original XML-RPC defect.
Evidence status: exploitation reported by the affected project’s advisory. Sergiu Gatlan’s November 18 reporting corroborates Apache’s warning. The reviewed sources identify no attacker, campaign details or confirmed number of compromised servers.
Install the repair, or stop the parsing path
Roller 6.1.6 or later fixes this particular issue. The repaired code disables extension types and rejects XML-RPC requests when the feature is disabled. Apache currently lists 6.1.7 as its best available release. That release also fixes separate vulnerabilities affecting 6.1.6, so the older minimum is not the preferred upgrade target.
For administrators who cannot upgrade immediately, Apache documents two temporary alternatives:
- Set
enabledForExtensionstofalseinWEB-INF/web.xml, then restart Roller. - Or remove the
/roller-services/xmlrpcservlet mapping, then restart Roller.
These alter whether dangerous request data reaches the parser. Changing the administration checkbox alone leaves the earlier parsing stage exposed. Removing the mapping also removes that remote-call interface, so check dependent publishing clients before making the change.
Use the current release notes to plan the upgrade and its behavior changes. Apache’s security policy says older release lines are not patched in place; the supported repair is an upgrade.
A patched server can still need investigation
For a previously reachable, vulnerable instance:
- Confirm the deployed release and completed restart, including every application instance behind a load balancer.
- Preserve relevant application and access logs before routine cleanup removes evidence.
- Investigate unexpected files, processes and account changes. These are general incident-response checks, not published indicators specific to this campaign.
- If compromise is found, scope recovery and credential replacement to the access obtained. Installing a repair alone cannot establish that the earlier exposure caused no damage.
Caveat: Apache reports active exploitation but has not published a complete incident account or campaign-specific detection guidance. The mitigation and version boundaries come from the project’s advisory, not a measured compromise count.