AEGLIX News
A critical unauthenticated deserialization vulnerability in Apache Roller's XML-RPC endpoint is being actively exploited, allowing remote attackers to execute arbitrary code without authentication, according to security advisories and catalog records. The flaw affects the open-source, Java-based blogging platform and stems from the endpoint's handling of vendor extension types before any authentication checks occur.
Apache Roller, an open-source Java blogging platform, contains a critical unauthenticated deserialization vulnerability in its XML-RPC endpoint that can result in remote code execution. The flaw, tracked as CVE-2026-129448, affects versions 4.0.0 through 6.1.4 and is identical to CVE-2026-82384, which had previously listed only version 6.1.5 as impacted. The XML-RPC endpoint processes vendor extension types and deserializes them prior to authenticating the requester, establishing a pre-authentication attack surface. Security researcher n0mi1k discovered the flaw, and Matt Raible is acknowledged for reporting it.
Catalog records confirm the deserialization of untrusted data allows unauthenticated remote code execution. The vulnerability is actively exploited in the wild. Disabling XML-RPC in the administration UI is insufficient mitigation because older versions deserialize the request before checking that setting, leaving the attack vector open even when the feature appears disabled.
The recommended remediation is to upgrade to Apache Roller 6.1.6 or later, a release that disables extension types and rejects XML-RPC requests when the XML-RPC feature is turned off. For environments where an immediate upgrade is not feasible, administrators can set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and then restart Roller.
Report prepared 2026-11-18 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.