Apache Roller XML-RPC Deserialization Flaw Resurfaces as CVE-2026-129448, Now Under Active Exploitation
A September fix for Apache Roller's XML-RPC deserialization bug covered only one version; the flaw got a new CVE covering 4.0.0-6.1.4 and is now being actively exploited.
Overview
Apache Roller, an open-source blogging platform written in Java, according to Security Affairs, has a critical unauthenticated remote-code-execution flaw that is being actively exploited, the Apache Software Foundation disclosed. The flaw, tracked as CVE-2026-129448, is a near-duplicate of a bug for which Apache had already shipped a narrower fix in September, and this time the foundation says the affected range is far larger than it first reported.
What We Know
The GitHub Security Advisory describes the issue as “Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4” that “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.” The flaw carries a CVSS 3.1 base score of 9.8, according to both The Hacker News and the GitHub advisory.
Apache says CVE-2026-129448 “is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected,” according to the GitHub advisory, and that “this issue is being actively exploited,” according to both BleepingComputer and the GitHub advisory. Neither Apache nor the outlets covering the disclosure specified when the exploitation began, which attackers are behind it, or which organizations have been targeted.
The original, narrower issue, CVE-2026-82384, was disclosed on the oss-security mailing list on September 25, 2026, in a post from Apache Roller committer David M. Johnson, according to the mailing list archive. That advisory credited researcher n0mi1k with the discovery and described a flaw limited to version 6.1.5, in which “the servlet is mapped unconditionally, so parsing occurs even when the global XML-RPC feature is set to disabled,” according to the GitHub advisory for CVE-2026-82384. The fix merged into the Roller codebase on September 5, 2026, under the title “Disable vendor extension types on the XML-RPC servlet,” according to the pull request, on the reasoning that “a disabled API is closed at the endpoint instead of relying on per-handler checks,” per the same pull request.
n0mi1k is again credited with discovering the broader issue behind CVE-2026-129448, with Matt Raible credited as the one who reported it to the project, according to both The Hacker News and Security Affairs. Raible had already reviewed and approved the original fix in pull request #171 in September, before the broader scope of the issue was identified.
Apache recommends upgrading to Roller 6.1.6 or later, which “disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled,” according to the GitHub advisory. For deployments that cannot upgrade immediately, the advisory recommends setting “enabledForExtensions” to “false” in WEB-INF/web.xml, or removing the “/roller-services/xmlrpc” servlet mapping and restarting Roller, according to both BleepingComputer and the GitHub advisory. The advisory specifically warns that “disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting,” a caveat also noted by Security Affairs.
NVD’s record for CVE-2026-129448 lists the advisory as published on November 17, 2026, a day before BleepingComputer, The Hacker News and Security Affairs reported on it on November 18.
What We Don’t Know
Apache has not disclosed when attackers began exploiting CVE-2026-129448, what techniques they are using, or which organizations, if any, have been compromised. It also remains unclear how long the broader 4.0.0-6.1.4 version range was vulnerable before the September patch, released only for 6.1.5, left most other affected versions unaddressed, or how Apache identified that the fix needed to cover additional versions.