Skip to main content
Emerging ThreatsMalware & Ransomware

Apache Roller Flaw Exploited in Wild, No Authentication Required

Empty server room with rows of computer servers and a single unoccupied workstation.

CVE-2026-129448 (CVSS score: 9.8) is a critical, unauthenticated deserialization flaw in Apache Roller that the Apache Software Foundation says "is being actively exploited."

CVE-2026-129448: unauthenticated deserialization in Apache Roller

Project maintainers at the Apache Software Foundation (ASF) have disclosed that Apache Roller—a Java-based, open-source blogging platform—contains a deserialization vulnerability in its XML-RPC endpoint. "Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code," the maintainers said. They added that "The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester."

Affected releases and connection to an earlier patch

ASF lists the vulnerable range as Apache Roller versions 4.0.0 through 6.1.4. The foundation also noted that this vulnerability is the same as CVE-2026-82384, which carried the same CVSS score of 9.8 and was patched in September 2026. That earlier advisory had explicitly listed only Apache Roller 6.1.5 as affected.

Active exploitation and what ASF disclosed

ASF stated plainly: "This issue is being actively exploited." Beyond that sentence, the foundation did not provide details about the nature of the exploitation or the identity of potential victims. The maintainers credited security researcher n0mi1k with discovering the flaw and acknowledged Matt Raible for reporting it.

Mitigation: upgrade to 6.1.6 or apply configuration workarounds

ASF's recommended fix is to upgrade to Apache Roller 6.1.6 or later. The 6.1.6 release disables the vendor extension types that enable the unsafe deserialization and adds logic to reject XML-RPC requests when the XML-RPC feature is disabled.

For operators who cannot apply the upgrade immediately, ASF outlined two configuration mitigations: set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping and then restart Roller. The foundation warned that disabling XML-RPC in the administration UI is insufficient for older installs because those versions "deserialize the request before checking that setting."

What Apache Roller administrators, enterprise procurement teams, and adversaries will watch

  • Apache Roller administrators and site operators: Immediate priorities are installing Roller 6.1.6 or applying the web.xml and servlet-mapping mitigations, then restarting the application. Administrators will also need to verify whether older UI controls for XML-RPC are effective in their deployments, because ASF warns the UI toggle may not prevent deserialization on older versions.
  • Enterprise procurement and platform teams: Buyers and platform owners that host or purchase services based on Apache Roller will need to confirm the version in use across hosted instances and managed services, and accelerate patch or configuration changes where 4.0.0 through 6.1.4 are present.
  • Adversaries and threat actors: ASF's confirmation of active exploitation signals that attackers have recognized both the high-impact nature of unauthenticated remote code execution and the practical reach of vulnerable Roller instances; attackers will likely continue to probe exposed XML-RPC endpoints until operators apply the recommended mitigations.

The disclosure from ASF leaves little ambiguity about risk and the immediate step operators must take: upgrade or disable the risky XML-RPC handling. ASF did not share any details on how the vulnerability is being exploited, or who is being targeted as part of these efforts, so defenders must assume that confirmed exploitation could be broad and automated. The simplest, clearest corrective action offered by the project maintainers is therefore the recommended path: move to Apache Roller 6.1.6 or later and, where upgrades are delayed, implement the web.xml or servlet-mapping mitigations and restart Roller.

Original story