A critical deserialization flaw in Apache Roller, the open-source Java blogging platform, lets an unauthenticated remote attacker run arbitrary code on the server. The bug, tracked as CVE-2026-129448, is in Roller’s XML-RPC endpoint. That endpoint accepts vendor extension types and deserializes them before it checks who sent the request. The flaw is rated 9.8 out of 10 on the CVSS scale.
The issue is being actively exploited. CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-20 and gave US federal agencies a deadline of 2026-11-23. Administrators running Roller should upgrade or apply the vendor’s workaround immediately.
What’s affected
According to the NVD record, Apache Roller versions 4.0.0 through 6.1.4 are affected.
This CVE covers the same underlying vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. CVE-2026-129448 extends the affected range back to the 4.x releases. Taken together, the two records mean every release from 4.0.0 through 6.1.5 should be treated as vulnerable.
The vendor recommends upgrading 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 turned off.
How serious is it
The CVE Numbering Authority scored the flaw 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms:
- Attack vector: Network. It can be exploited remotely over the network.
- Attack complexity: Low. No special conditions are needed.
- Privileges required: None. No account or login is needed, because deserialization happens before authentication.
- User interaction: None. Nobody has to click anything.
- Impact: High for confidentiality, integrity and availability. A successful attacker can execute code and could take full control of the Roller server.
The weakness is classified as CWE-502, Deserialization of Untrusted Data.
Is it being exploited?
Yes. The NVD description states that the issue is being actively exploited. CISA has confirmed exploitation by adding CVE-2026-129448 to the KEV catalog on 2026-11-20. Whether the flaw has been used in ransomware campaigns is listed as “Unknown.”
Under CISA’s directive, US federal civilian agencies must act by 2026-11-23. The required action is to:
- apply mitigations in accordance with vendor instructions, in line with BOD 26-04 (Prioritizing Security Updates Based on Risk) and CISA’s Forensics Triage Requirements;
- follow applicable BOD 26-04 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA also says stakeholders are responsible for evaluating each asset’s internet exposure.
What to do
- Upgrade to Apache Roller 6.1.6 or later. This is the vendor’s recommended fix.
- If you cannot upgrade right away, use one of the vendor’s workarounds and then restart Roller:
- set
enabledForExtensionstofalseinWEB-INF/web.xml, or - remove the
/roller-services/xmlrpcservlet mapping.
- set
- Do not rely on the admin setting. Disabling XML-RPC in the administration UI does not protect you. Older versions deserialize the request before they check that setting.
- Restrict exposure. Where possible, block or limit access to
/roller-services/xmlrpcat a reverse proxy or firewall, especially on internet-facing servers. - Check for compromise. The flaw is being exploited, so review internet-exposed Roller servers for signs of intrusion. Look for unexpected processes, files or outbound connections, and unusual requests to the XML-RPC endpoint.

