Apache Roller: prove the fix on the XML-RPC route
Apache has confirmed exploitation of a flaw that allows remote code execution in Roller before authentication. Response must verify the deployed application and XML-RPC route, including when the administration interface shows the feature as disabled.
Leggi in portogheseIn this article
By Pentesty
Separate the news date from the vulnerability scope
Apache’s CVE-2026-129448 record, published on November 17, 2026, covers Roller 4.0.0 through 6.1.4. It states that the vulnerability is being actively exploited. It connects the issue to CVE-2026-82384, whose earlier record listed only version 6.1.5. These are two references for the same flaw, with complementary version scopes.
Apache describes deserialization of untrusted data at the XML-RPC endpoint before authentication. This allows remote code execution without credentials. The record consulted does not identify operators, compromised organizations or attack counts. Reported exploitation warrants response priority, but does not establish that a particular installation was compromised.
Inventory the application that actually serves traffic
Locate Roller instances, owners, published addresses and components forwarding requests. Include replicas, old environments and applications accessible only from the internal network. Associate each address with a version obtained from the deployed artifact, recording when and how the evidence was collected. A central inventory entry needs to match the running process.
The prescribed fix is Roller 6.1.6 or later. When consulted for this analysis on November 18, the official downloads page presented 6.1.7 as the best available release. Review the selected release notes, test migration and check signatures or checksums against official files. Record the approved rollback plan as well.
Make the configuration reach the process
For organizations unable to upgrade immediately, Apache advises setting enabledForExtensions to false in WEB-INF/web.xml or removing the /roller-services/xmlrpc servlet mapping, followed by a restart. These temporary alternatives require assessment in the installation’s context. Disabling XML-RPC only in the administration interface is insufficient in affected releases because deserialization happens before that check.
Keep the previous configuration, approved change and restart evidence. Verify the configuration loaded by every instance and identify legitimate XML-RPC consumers that will be affected. An old replica returning to the load balancer can invalidate remediation even when the first instance passed validation.
Validate without reproducing exploitation
In an authorized environment, use a benign request to observe whether the route was removed or responds according to the selected release and policy. Correlate the response with the application and its logs. A proxy block demonstrates that control’s behavior; add server configuration evidence to assess internal paths. Malicious objects are unnecessary for documenting acceptance.
Also check login, publishing and blog reading with test data. Record expected and observed results and the person approving them. Our analysis of Java4Shell and the effective JVM addresses another layer: patching Java does not replace updating Roller. Maintain separate evidence for each change.
Investigate when concrete indicators appear
Preserve available logs, retention periods and administrative changes. If unexpected processes, content modifications or other indicators appear, refer them to the response team to establish the relevant period and systems. Missing records do not prove the absence of compromise. Technical acceptance of the fix and closure of an investigation need their own criteria.
The approach to route and active configuration validation offers a related way to organize evidence without equating the products’ vulnerabilities. Give the service owner a record of covered instances, final version, route behavior, functional tests, limitations and the next follow-up. Agree on another verification after the next deployment cycle to detect the return of old artifacts or configurations.
Frequently asked questions
Which Roller releases need attention?
CVE-2026-129448 covers 4.0.0 through 6.1.4. The earlier reference, CVE-2026-82384, lists 6.1.5 for the same flaw. Apache recommends 6.1.6 or later.
Does disabling XML-RPC in the dashboard resolve it?
Apache says this is insufficient in affected releases. The code deserializes data before checking that option; apply the fix or specified configuration mitigation and restart.
Must I run an exploit to validate remediation?
No. The deployed artifact, loaded configuration, restart and benign requests can document expected behavior, alongside functional tests and explicit limitations.
Does the alert confirm a breach at my company?
No. Apache reports exploitation of the vulnerability without identifying every affected installation. A conclusion about your environment requires its own investigation and evidence.
Sources and references
- Apache CNA: CVE-2026-129448, originally published November 17, 2026
- Apache CNA: CVE-2026-82384, earlier record for Roller 6.1.5
- Apache Roller: downloads and integrity verification
Original Pentesty analysis, published November 18, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.