Vulnerability
Published 2026-11-17
Verified 2026-11-18

Apache Roller CVE-2026-129448 (CVSS 9.8): unauthenticated XML-RPC deserialization code execution in versions 4.0.0 through 6.1.4 is being actively exploited, Apache says; upgrade to 6.1.6

The Apache Roller project said on 17 November 2026 that deserialization of untrusted data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code, because the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester (CVE-2026-129448, CVSS 3.1 9.8, Critical) (source: Apache Roller).

Apache says this is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected, and that the issue is being actively exploited (source: Apache Roller). Apache recommends upgrading to Apache Roller 6.1.6 or later; users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller, and Apache says disabling XML-RPC in the administration UI is not enough because older versions deserialize the request before checking that setting (source: Apache Roller).

Apache credits n0mi1k (finder) and Matt Raible (reporter).

Product
Apache Roller (Java blog server) — XML-RPC endpoint
Versions
Apache Roller 4.0.0 through 6.1.4 (CVE-2026-129448); 6.1.5 (CVE-2026-82384, same flaw); fixed in 6.1.6 or later (per Apache)
CVSS
, CVSS 3.1, Apache; Apache severity: Critical
Exploited in Australia?
unknown
Patch to
Apache: upgrade to Apache Roller 6.1.6 or later. If you cannot upgrade right away, set "enabledForExtensions" to "false" in WEB-INF/web.xml or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller; disabling XML-RPC in the admin UI is not enough on older versions.

vulnerabilities