Apache Warns of Actively Exploited RCE Flaw in Apache Roller

Apache has confirmed the active exploitation of a critical flaw in the Apache Roller server. A fix is available in version 6.1.6.

The Apache Roller vulnerability identified as CVE-2026-129448 is being actively exploited, according to the Apache Software Foundation. The flaw allows an unauthenticated remote attacker to execute arbitrary code on a vulnerable server through the XML-RPC endpoint. Administrators of publicly accessible installations should prioritize upgrading to Apache Roller 6.1.6 or deploying the recommended temporary mitigation.

Apache published the advisory on November 17, 2026. The issue involves unsafe deserialization in the XML-RPC interface and, according to the security advisory, affects Roller versions from 4.0.0 through 6.1.5.

The Apache Roller vulnerability also affects version 6.1.5

Apache originally describes CVE-2026-129448 as affecting releases 4.0.0 through 6.1.4. The advisory also states that it is the same flaw as CVE-2026-82384, under which Roller 6.1.5 was separately identified as vulnerable. In practical terms, all versions from 4.0.0 through 6.1.5, inclusive, should therefore be considered affected.

The attack does not require authentication. If a vulnerable Apache Roller server is accessible over the network, an attacker may achieve remote code execution through flawed request processing on the XML-RPC interface. Apache explicitly confirmed that attackers are already exploiting the flaw.

Apache has not disclosed who is carrying out the attacks, how many servers were compromised, or any indicators of compromise. Independent technical evidence of specific incidents is also not publicly available. The confirmation of active exploitation comes from an Apache project statement.

The Apache Roller vulnerability is fixed in version 6.1.6

The fix is included in Apache Roller 6.1.6 or a newer release. Updating is the recommended solution for all affected deployments.

If an immediate update is not possible, Apache lists two temporary mitigation options:

  • disable the enabledForExtensions setting in WEB-INF/web.xml,
  • or remove the /roller-services/xmlrpc mapping.

The server must be restarted after either change. Importantly, disabling XML-RPC in the administration interface alone is not sufficient. According to Apache, vulnerable releases process the request before checking this setting.

What administrators should check

Administrators should determine whether they are running Apache Roller version 4.0.0 through 6.1.5, particularly on servers accessible from the internet. They should then confirm an upgrade to version 6.1.6 or newer. If an update is not yet feasible, they should verify that the XML-RPC endpoint has been removed or securely blocked according to Apache’s procedure.

Further developments may lead to CVE-2026-129448 or the related CVE-2026-82384 being added to the U.S. CISA’s Known Exploited Vulnerabilities catalog. Any technical details of the attacks, indicators of compromise, or information about the attackers will also be relevant if Apache or security researchers publish them.

Sources

  • Apache Roller GitHub pull request #171 – The project’s primary record documents the change that disables XML-RPC vendor extensions and closes the endpoint when the service is disabled.
  • Apache Roller 6.1.6 release – Confirms the existence of the Apache Roller 6.1.6 corrective release.
  • Apache mailing list advisory – The official Apache advisory is the source for claims about active exploitation, the scope of CVE-2026-129448, and the recommended mitigations.
  • BleepingComputer – Independently corroborates Apache’s current warning and states that details about the attackers and the extent of the compromises were not disclosed.

Verified and updated: November 18, 2026 15:42

Sharing