Apache has pushed out security updates to address a critical vulnerability in Roller that threat actors are actively leveraging to execute code on unpatched systems. Roller is an open-source, Java-based group-blogging application with a relatively small installed base compared to mainstream content management and blogging solutions.

Despite its niche status, Apache has designated the flaw—identified as CVE-2026-129448—as being actively exploited in the wild. The company has not disclosed specifics about these ongoing campaigns, such as the identity of the attackers or the number of compromised installations.

The vulnerability stems from unsafe handling of serialized data in the XML-RPC endpoint. According to Apache's Tuesday advisory, "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 XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester." The advisory further notes that "This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited."

image

Immediate remediation steps

Roller administrators should upgrade immediately to Apache Roller 6.1.6 or later, which disables the extension types and rejects malicious XML-RPC requests by turning off the XML-RPC feature entirely.

For organizations unable to patch right away, Apache offers temporary workarounds to mitigate CVE-2026-129448:

  • Set "enabledForExtensions" to "false" in WEB-INF/web.xml
  • Remove the "/roller-services/xmlrpc" servlet mapping
  • Restart the Roller service

A critical caveat: disabling XML-RPC through the administration interface alone is insufficient to stop attacks. Older versions of Roller deserialize incoming requests before validating whether the XML-RPC setting is enabled, meaning the configuration change alone will not block exploitation.

Broader context of Apache vulnerabilities

This incident fits into a larger pattern of Apache software flaws being weaponized. In April, the US Cybersecurity and Infrastructure Security Agency (CISA) identified a 13-year-old Apache ActiveMQ vulnerability (CVE-2026-34197) as actively exploited and directed federal agencies to patch within two weeks.

Earlier this month, Apache released a fix for a critical remote code execution flaw in the HTTP/2 module of Apache HTTP Server that could be exploited by unauthenticated attackers on vulnerable installations.

Since November 2021, CISA has cataloged 41 Apache vulnerabilities that have been exploited in active attacks, with eight of those also leveraged by ransomware operators.