← cd ../blog

CVE-2026-129448: unauthenticated RCE in Apache Roller, exploited in the wild

A pre-auth XML-RPC deserialization flaw (CVSS 9.8) gives attackers code execution on Apache Roller. Impact, prerequisites, exposure checks and the exact fix.

The first of three critical RCE flaws I’m covering this week, and the only one already under active exploitation. If you run Apache Roller, this is a drop-everything patch. For the other two, see the Apache HTTP/2 race condition and the Linux kernel TCP use-after-free; for the wider picture, the 2026 RCE field guide lists ten.

Scope and ethics. The steps below are exposure detection and remediation for systems you own or are authorized to assess — not a weaponized exploit. Working PoCs live behind the references, for use in a lab you control.

Description

Apache Roller is a Java blogging platform. Its XML-RPC endpoint deserializes vendor-extension types before it authenticates the request. Deserializing untrusted data on a pre-auth code path is a classic road to remote code execution: an attacker who can reach the endpoint controls the object graph that gets instantiated. The Apache Software Foundation notes this is the same underlying weakness as CVE-2026-82384 (patched September 2026) that was incompletely fixed — CVE-2026-129448 is the proper closure.

Impact

Full remote code execution as the Roller service account: site defacement, theft of posts, drafts and user data, and a foothold for lateral movement into whatever network the blog host sits in. The ASF confirms the flaw is being actively exploited, so any exposed, unpatched instance should be treated as potentially already compromised.

Prerequisites (for the attack to work)

  • Network reachability to the Roller app, specifically the /roller-services/xmlrpc servlet.
  • A vulnerable version: Apache Roller 4.0.0 through 6.1.4.
  • No credentials. No user interaction.

Steps to reproduce (exposure validation)

On a host you administer, confirm whether the endpoint is reachable and which version is deployed:

# 1) Is the XML-RPC endpoint exposed? A 200/405 to POST means it's present.
curl -s -o /dev/null -w "status=%{http_code}\n" \
  -X POST https://blog.example.com/roller-services/xmlrpc

# 2) Confirm the deployed version from the WAR manifest on your own server
unzip -p /opt/roller/roller.war META-INF/MANIFEST.MF | grep -i version

# 3) Spot unexpected children of the Roller/JVM process (post-exploitation signal)
ps --ppid "$(pgrep -f roller | head -n1)" -o pid,cmd 2>/dev/null

If the endpoint answers and the version is ≤ 6.1.4, you are exposed. For a full proof-of-concept, build a matching version in an isolated VM and use the researcher references below — never against production or third-party systems.

Remediation

  1. Upgrade to Apache Roller 6.1.6 or later. This is the real fix.
  2. If you genuinely cannot patch yet, apply an official workaround and restart Roller:
    • Set enabledForExtensions to false in WEB-INF/web.xml, or
    • Remove the /roller-services/xmlrpc servlet mapping entirely.
    • Do not rely on disabling XML-RPC in the admin UI — older versions deserialize the request before checking that setting.
  3. Because exploitation is active, hunt before you trust the patch: review the Roller account for unexpected child processes, new admin users, modified templates, and outbound connections from the app host.

References

Verify every version against the vendor advisory before acting. Published 20 Nov 2026.