The Apache Software Foundation warned that CVE-2026-129448, a critical remote code execution flaw in Apache Roller, is being actively exploited. The advisory, published November 17, widens the affected range to Roller 4.0.0 through 6.1.4 and says the vulnerability is the same one Apache patched in September under a different identifier.
An Unauthenticated Deserialization Flaw in the XML-RPC Endpoint
CVE-2026-129448 carries a CVSS score of 9.8. It is an unauthenticated deserialization flaw in Roller’s XML-RPC endpoint, which deserializes vendor extension types before it authenticates the requester. An attacker can therefore send a crafted request and reach code execution without credentials.
Apache’s notice states, “This issue is being actively exploited.” The foundation did not say who is attacking, which targets have been hit or how many servers are compromised.
Why Disabling XML-RPC in the Admin Interface Does Not Help
Turning off XML-RPC in the administrative interface does not close the hole. Older Roller versions deserialize the request before checking whether the feature is enabled, so the vulnerable code path runs regardless of the setting. Administrators who believed an interface toggle had protected them were not protected.
Credit and the Link to CVE-2026-82384
Researcher n0mi1k found the flaw, and Matt Raible reported it. Apache says it is the same issue as CVE-2026-82384, patched in September. That earlier notice listed only Roller 6.1.5 as affected. The new advisory expands the range to every version from 4.0.0 through 6.1.4, leaving a much larger set of installations that the original notice did not cover.
Patch and Workaround Options for Roller Administrators
The fix is to upgrade to Roller 6.1.6 or later. For administrators who cannot upgrade immediately, Apache lists two workarounds. One is to set “enabledForExtensions” to “false” in WEB-INF/web.xml. The other is to remove the “/roller-services/xmlrpc” servlet mapping. Either change requires a restart to take effect.
Because the September patch listed only Roller 6.1.5 as affected, administrators running 6.1.5 and every older release back to 4.0.0 should treat the November advisory as the authoritative scope. Apache published it on Tuesday, November 17, and The Hacker News, BleepingComputer and Security Affairs covered it the next day.
Neither workaround is a substitute for the upgrade, since both depend on administrators editing configuration and restarting the server, but they give operators of internet-facing blogs a way to cut off the vulnerable path while a move to 6.1.6 is planned.
Footprint and Wider Apache Exploitation Context
Roller is a niche blogging server, and Apache’s notice gives no estimate of how many installations run the affected 4.0.0 through 6.1.4 range, so the number of exposed installations is likely smaller than for mainstream Apache products. A successful attack still means full takeover of the affected server.
The disclosure follows earlier Apache problems this month. Apache fixed a critical mod_http2 remote code execution flaw earlier in November. CISA has added 41 Apache flaws to its Known Exploited Vulnerabilities catalog since November 2021, and eight of them have also been used by ransomware gangs.
A Patch That Understated the Affected Range
The sequence around this flaw raises a question about how vulnerability scoping was handled. A fix in September that named a single affected version, followed by a November advisory that extends the range back to 4.0.0 and reports exploitation, means that administrators running versions older than 6.1.5 had no notice that the September patch applied to them. Organizations that tracked only the original notice would have judged their older installations unaffected.
Apache has yet to say how many servers were hit, so the scale of the exploitation, and how long attackers had to act before the range was corrected, remains unknown.
