Apache Roller CVE-2026-129448: XML-RPC RCE Patch Guide

Apache Roller CVE-2026-129448 enables unauthenticated XML-RPC RCE. Check affected versions, upgrade to 6.1.7, and contain exposed servers.

William OGOU
4 min read
Share
On this page7 sections

On 17 November 2026, the Apache Software Foundation (ASF) published the Common Vulnerabilities and Exposures (CVE) record CVE-2026-129448, an unauthenticated Remote Code Execution (RCE) flaw in Apache Roller rated 9.8 under the Common Vulnerability Scoring System (CVSS) 3.1. Apache reports active exploitation, so exposed installations need immediate containment and patching.

The vulnerable path is /roller-services/xmlrpc, Roller’s XML Remote Procedure Call (XML-RPC) endpoint. Older releases deserialise attacker-controlled extension types before authentication. Prioritise the deployed application, not just an administration setting.

What to Remember

  • Affected: Roller 4.0.0 through 6.1.4; Roller 6.1.5 has the same flaw under CVE-2026-82384.
  • Fixed: Roller 6.1.6 or later; 6.1.7 is the current Generally Available (GA) release.
  • Workaround: Disable extension types in WEB-INF/web.xml or remove the servlet mapping, then restart.
  • Boundary: Attackers need endpoint reachability, not credentials; execution inherits Roller’s runtime permissions.

How XML-RPC Deserialisation Enables Code Execution

The XML-RPC library accepts non-standard vendor extension types, allowing attacker-controlled bytes to be deserialised during request parsing. Authentication and the older XML-RPC enablement check occur later. The Common Weakness Enumeration (CWE) classifies the bug as CWE-502: Deserialization of Untrusted Data.

Successful RCE could expose application secrets, database contents or internal services accessible to Roller. Root access is not guaranteed: consequences depend on the servlet-container account and runtime identity permissions. For prevention beyond patching, apply secure code review checks for trust boundaries.

Affected and Fixed Apache Roller Versions

Roller versionXML-RPC vulnerability statusAction
4.0.0 through 6.1.4Affected by CVE-2026-129448Upgrade
6.1.5Same flaw, CVE-2026-82384Upgrade
6.1.6First fixed release for the XML-RPC RCEPrefer current release
6.1.7Current GA release; includes the fixRecommended target

The two CVEs describe the same flaw across different version ranges, not a bypass of the 6.1.6 patch.

Patch or Temporarily Close XML-RPC

Permanent fix: upgrade Apache Roller

Install Roller 6.1.7 from Apache downloads; 6.1.6 is the minimum fixed version for the XML-RPC flaw. Verify Apache’s signatures or checksums, back up the database and configuration, and redeploy every instance.

The upstream fix disables extension types and rejects disabled XML-RPC requests before parsing. Confirm the deployed version after restart, including replicas and rollback images. As with Node.js runtime vulnerability patching, an updated source tree does not prove production is fixed.

Temporary workaround: change deployed configuration

In the existing XML-RPC servlet definition inside WEB-INF/web.xml, change the existing enabledForExtensions value to false. The fragment illustrates the parameter only; do not add a duplicate servlet or parameter.

xml
<init-param>
	<param-name>enabledForExtensions</param-name>
	<param-value>false</param-value>
</init-param>

Alternatively, remove the /roller-services/xmlrpc servlet mapping if XML-RPC is unused. Restart Roller or the servlet container, then verify the deployed configuration. Removing the mapping disables XML-RPC clients; disabling extensions preserves standard XML-RPC values.

Proxy blocking is additional containment, not the patch; cover direct backend routes too. Switching XML-RPC off in the administration interface alone is insufficient.

Minimal Triage for Exposed Roller Servers

  1. Inventory Roller versions, context paths and direct origin access. Preserve proxy, servlet and application logs.
  2. Review requests to /roller-services/xmlrpc. Correlate timestamps with unexpected Java child processes, modified application files, unusual outbound traffic or database activity.
  3. Requests alone do not prove compromise. If compromise is confirmed, isolate and rebuild affected instances, then rotate exposed runtime credentials.

Conclusion: Close the Parsing Boundary

Patch Roller, close unused XML-RPC endpoints, and verify every running instance. A configuration workaround buys time but does not replace the upgrade.

Re-check endpoint access after redeployment; old replicas and rollback images can reintroduce exposure.

For remediation support, contact me on LinkedIn or [email protected].

FAQ

Frequently Asked Questions (FAQ)

Which Apache Roller versions are affected by CVE-2026-129448?

CVE-2026-129448 covers Roller 4.0.0 through 6.1.4. Roller 6.1.5 has the same flaw under CVE-2026-82384.

Is Apache Roller XML-RPC RCE actively exploited?

Apache explicitly reports active exploitation. The advisory does not identify a public attacker campaign.

Does disabling XML-RPC in the administration interface fix the vulnerability?

No: older Roller releases deserialise requests before checking the administration setting. Set enabledForExtensions to false in WEB-INF/web.xml and restart Roller, or upgrade to 6.1.6 or later.

Which Apache Roller release fixes the XML-RPC vulnerability?

Roller 6.1.6 is the first fixed release. Roller 6.1.7 is the current recommended upgrade target.

Does Apache Roller RCE automatically provide root access?

No: execution inherits the Roller process permissions. Review runtime account access to secrets, databases and internal services.

Resources