Advisory

CVE-2026-129448 (CRITICAL 9.8): Apache Roller RCE via XML-RPC Deserialization — Patch Now

A critical unauthenticated remote code execution vulnerability in Apache Roller versions 4.0.0 through 6.1.4 allows attackers to execute arbitrary code by sending a crafted XML-RPC request that the server deserializes before performing any authentication check. This vulnerability is listed in the CISA Known Exploited Vulnerabilities catalog and is being actively exploited.

TL;DR: Upgrade Apache Roller to version 6.1.6 or later immediately. If an immediate upgrade is not possible, set <code>enabledForExtensions</code> to <code>false</code> in <code>WEB-INF/web.xml</code> or remove the <code>/roller-services/xmlrpc</code> servlet mapping, then restart Roller — disabling XML-RPC in the admin UI alone is insufficient.

What Is the Flaw?

CVE-2026-129448 is a Deserialization of Untrusted Data vulnerability (CWE-502) in Apache Roller, an open-source Java blog server. It carries a CVSS 3.1 score of 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, meaning it is exploitable over the network with no special privileges, no user interaction, and low complexity.

The root cause lies in the XML-RPC endpoint (/roller-services/xmlrpc). This endpoint accepts vendor extension types embedded in XML-RPC requests and deserializes them before authenticating the requester. Deserialization of attacker-controlled data in Java can trigger execution of arbitrary code through gadget chains present in the application's classpath — a well-understood and dangerous class of vulnerability.

The NVD advisory notes that this CVE covers the same underlying vulnerability as CVE-2026-82384, which had been recorded as affecting only Apache Roller 6.1.5. CVE-2026-129448 corrects that scope by documenting the full range of affected versions: 4.0.0 through 6.1.4.

Critically, disabling XML-RPC through the Roller administration UI is not a sufficient mitigation in older versions, because those versions deserialize the request payload before consulting that setting.

Who and What Is Affected?

Any deployment of Apache Roller versions 4.0.0 through 6.1.4 (inclusive) with the XML-RPC servlet reachable is vulnerable. This applies regardless of whether XML-RPC has been disabled in the application's administration panel.

  • Internet-facing Roller instances are at the highest risk given the network-accessible, unauthenticated nature of this flaw.
  • Intranet or privately hosted Roller instances remain vulnerable to attack from any network-adjacent or internal threat actor who can reach the XML-RPC endpoint.
  • Organizations that have customized or packaged Roller as part of a larger platform should verify whether the underlying Roller version falls within the affected range.

Apache Roller 6.1.5 was identified separately under CVE-2026-82384 as also affected by the same underlying vulnerability. Users running 6.1.5 should consult that advisory in addition to this one.

Impact

Successful exploitation of CVE-2026-129448 gives an unauthenticated remote attacker arbitrary code execution in the security context of the Roller application server process. The CVSS scores reflect a complete compromise across all three security dimensions:

  • Confidentiality (High): An attacker can read any data accessible to the server process, including blog content, credentials, and configuration secrets.
  • Integrity (High): An attacker can modify or delete data, plant malicious content, or alter server configuration.
  • Availability (High): An attacker can crash or render the server unavailable.

Because no authentication is required and exploitation complexity is rated low, this vulnerability is accessible to a wide range of threat actors. CISA has added CVE-2026-129448 to the Known Exploited Vulnerabilities (KEV) catalog, with the catalog entry dated 2026-11-20. The NVD description explicitly states that this issue is being actively exploited. Organizations should treat this as an urgent, high-priority remediation.

What To Do Now

CISA's KEV required action directs affected organizations to apply vendor mitigations in accordance with vendor instructions, consistent with BOD 26-04 guidance. The following actions are ordered by effectiveness and immediacy:

  1. Upgrade to Apache Roller 6.1.6 or later (preferred). Version 6.1.6 disables the vulnerable extension types and rejects XML-RPC requests when the XML-RPC feature is disabled, addressing the flaw at its root. Obtain the release from the official Apache Roller project site.
  2. If an immediate upgrade is not possible — set enabledForExtensions to false. Edit WEB-INF/web.xml, locate the XML-RPC servlet configuration, set the enabledForExtensions parameter to false, and restart the Roller application. This prevents the vulnerable deserialization path from being triggered.
  3. Alternatively, remove the XML-RPC servlet mapping. Removing the /roller-services/xmlrpc servlet mapping from WEB-INF/web.xml and restarting Roller eliminates the exposed endpoint entirely.
  4. Do NOT rely solely on the administration UI toggle. Setting XML-RPC to disabled in the Roller admin interface is explicitly documented as insufficient for older versions, because deserialization occurs before that setting is checked.
  5. Network-layer controls. As a defense-in-depth measure (not a substitute for the above), consider restricting access to the /roller-services/xmlrpc path at the web application firewall or reverse proxy layer, particularly for internet-facing deployments.
  6. Review and assess exposure. Per CISA's KEV guidance, stakeholders are responsible for evaluating each asset's internet exposure and applying BOD 26-04 patching timelines accordingly. If mitigations cannot be applied, consider discontinuing use of affected versions.

Consult the NVD entry for CVE-2026-129448 and the CISA KEV catalog for the most current guidance and any additional references published by Apache.

How External Testing Surfaces This Exposure

Because CVE-2026-129448 is exploitable without any authentication, it represents precisely the type of vulnerability that external, unauthenticated security assessments are well-positioned to detect. A point-in-time external vulnerability scan or web application assessment targeting a Roller deployment can identify:

  • Whether the /roller-services/xmlrpc endpoint is reachable and responding.
  • The Apache Roller version in use, to determine whether it falls within the affected range (4.0.0–6.1.4).
  • Whether the endpoint accepts XML-RPC requests with vendor extension types — the prerequisite condition for exploitation.
  • Misconfigurations such as reliance on the admin UI toggle without the underlying web.xml change.

Organizations should ensure their external attack surface assessments explicitly cover Java-based blogging and publishing platforms, particularly legacy deployments that may not receive routine update attention. Identifying this exposure before an attacker does is the goal of any structured vulnerability assessment program.

Sources & further reading: NVD CVE-2026-129448 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, lists.apache.org, lists.apache.org, cve.org. This advisory contains no exploit code.

Frequently asked questions

Is just turning off XML-RPC in the Roller admin panel enough to protect my server?

No. For Apache Roller versions 4.0.0 through 6.1.4, disabling XML-RPC in the administration UI is explicitly documented as insufficient. These versions deserialize the XML-RPC request payload before they check whether XML-RPC is enabled in the settings. You must either upgrade to 6.1.6 or later, set <code>enabledForExtensions</code> to <code>false</code> in <code>WEB-INF/web.xml</code>, or remove the XML-RPC servlet mapping, and then restart Roller.

How does this relate to CVE-2026-82384?

CVE-2026-82384 documented the same underlying deserialization vulnerability but was recorded as affecting only Apache Roller 6.1.5. CVE-2026-129448 corrects and extends that scope, covering Apache Roller versions 4.0.0 through 6.1.4. If you are running version 6.1.5, you should consult both advisories.

Is this vulnerability being actively exploited?

Yes. The NVD description for CVE-2026-129448 states that this issue is being actively exploited. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-20. Organizations should treat remediation as urgent.

My Roller instance is not on the public internet. Am I still at risk?

Yes, though the degree of risk depends on who can reach the server. The CVSS vector is network-based with no authentication required, so any attacker who can reach the <code>/roller-services/xmlrpc</code> endpoint — whether from the internet, a corporate network, a VPN, or through a compromised internal host — can potentially exploit this vulnerability. Network segmentation reduces but does not eliminate risk; patching or applying the documented workarounds is still necessary.