The Apache Software Foundation has issued an urgent security advisory regarding a critical remote code execution (RCE) vulnerability in Apache Roller, an open-source Java-based blogging platform. The flaw, assigned the identifier CVE-2026-129448 and carrying a maximum CVSS severity score of 9.8, is currently being exploited in the wild.
The vulnerability stems from an insecure deserialization process within the platform’s XML-RPC endpoint. According to the foundation, the application attempts to process and deserialize vendor extension types provided in XML-RPC requests before verifying the identity of the requester. Because this validation occurs prior to authentication, an unauthenticated attacker can execute arbitrary code on a compromised server without needing valid credentials.
This security issue is not entirely new; it is a broader manifestation of a previously documented flaw, CVE-2026-82384. While that earlier advisory, released in September 2026, suggested the risk was limited to Apache Roller version 6.1.5, the foundation has confirmed that the scope is significantly wider. The vulnerability affects all versions of the software ranging from 4.0.0 through 6.1.4, as well as the previously identified 6.1.5 release.
The Apache Software Foundation has explicitly confirmed that the vulnerability is under active exploitation. While the organization has acknowledged the presence of these attacks, it has not released specific technical details regarding the threat actors involved, the identity of targeted organizations, or the specific methods used to weaponize the exploit.
To remediate the vulnerability, the foundation strongly recommends that all users upgrade their installations to Apache Roller version 6.1.6 or later. This updated release includes changes that disable the problematic vendor extension types and ensure that XML-RPC requests are properly rejected if the feature is disabled.
For administrators unable to perform an immediate upgrade, the foundation has provided specific manual workarounds. These include setting the enabledForExtensions parameter to false within the WEB-INF/web.xml configuration file or removing the /roller-services/xmlrpc servlet mapping entirely. In either case, a full restart of the Apache Roller service is required for the changes to take effect.
Security experts emphasize that simply disabling the XML-RPC feature through the platform’s administrative user interface is insufficient for older versions of the software. Because the vulnerable code path executes the deserialization process before checking the administrative configuration, the application remains exposed even if the feature appears to be turned off in the settings.
The discovery of this vulnerability is credited to security researcher n0mi1k, with Matt Raible credited for reporting the issue to the project maintainers. Given the confirmed active exploitation, security teams are urged to prioritize the identification of all internal and internet-facing Apache Roller instances to ensure they are patched or properly configured, as even internal servers can serve as significant entry points for attackers once they have established a foothold within a corporate network.





