Apache Roller, a widely-used open-source blogging platform written in Java, is facing a serious security threat. A critical vulnerability (CVE-2026-129448) has been discovered that allows unauthenticated remote attackers to execute arbitrary code. The flaw resides in how Roller handles XML-RPC requests and has already been found in active exploitation.
What’s the Vulnerability?
The issue is due to insecure deserialization of untrusted data through Roller’s XML-RPC endpoint in versions 4.0.0 through 6.1.4. The endpoint accepts vendor extension types and improperly processes them before any authentication checks occur. Because of this, someone with no credentials can send a crafted message to trigger remote code execution.
Severity, Discovery, and Exploitation
This security gap has been assigned a CVSS score of 9.8, marking it as critical. Notably, the vulnerability is tied to a previously disclosed issue, CVE-2026-82384, which had been thought to affect only Roller version 6.1.5. However, it now appears that the same weakness spans versions 4.0.0 to 6.1.4. Project maintainers confirm that the flaw is already being exploited in the wild; however, details about who is being targeted or how attacks are unfolding remain undisclosed.
Patching and Mitigation
To close the breach, Roller users should immediately upgrade to version 6.1.6 or later. In these newer builds, the dangerous extension types are disabled by default, and any XML-RPC requests are rejected when XML-RPC support is turned off.
For instances where updating isn’t possible right away, temporary mitigations include setting the “enabledForExtensions” parameter to “false” in WEB-INF/web.xml, or removing the XML-RPC servlet mapping at /roller-services/xmlrpc. A full restart of Roller is necessary for changes to take effect. Importantly, disabling XML-RPC via the administration UI alone is insufficient—older versions still deserialize data before checking that setting.
Who Found It
The researcher known as n0mi1k originally uncovered the problem. Another contributor, Matt Raible, is credited with reporting the finding.
With this vulnerability being actively exploited, the implications for blogs and content platforms relying on Apache Roller are dire. Remote code execution at this scale offers attackers complete takeover potential, and because the flaw bypasses authentication, even minimal exposure can be catastrophic. The immediate call to action is clear: upgrade to Roller 6.1.6 or patch your configuration to disable the risky endpoints. Going forward, maintainers and users alike should watch closely for attack patterns tied to XML-RPC misuse and ensure any serialization of external data is tightly controlled.