CVE-2026-129448 Security Alert: CRITICAL Vulnerability

Urgent: CVE-2026-129448 requires immediate attention.

· 7 min read

Executive Summary

CVE-2026-129448 is a critical remote code execution flaw in Apache Roller affecting versions 4.0.0 through 6.1.4. An unauthenticated attacker can send a crafted XML-RPC request that is deserialized before authentication, allowing arbitrary code execution on the server. This issue is the same underlying bug as CVE-2026-82384, but the affected range is broader than previously reported. It is being actively exploited.

If you run Roller for a blog, internal publishing site, or small team CMS, treat this as an emergency. The safest fix is to upgrade to Apache Roller 6.1.6 or later. If you cannot patch immediately, disable the vulnerable XML-RPC path at the server config level and restart Roller.

Immediate Action

  • Upgrade now to Apache Roller 6.1.6+ as soon as possible. This version disables the extension types and rejects XML-RPC requests when the feature is off.
  • Do not rely on the admin UI alone to disable XML-RPC; older versions deserialize requests before checking that setting.
  • Emergency mitigation: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller.
  • Isolate the service temporarily: restrict access to the Roller host at the firewall / reverse proxy, especially from the public internet.
  • Check for compromise if the service was exposed: review logs, new accounts, unexpected processes, webshells, and outbound connections.
  • See the vendor advisory: Apache Roller security advisory.

Affected Versions

  • Apache Roller 4.0.0 through 6.1.4 are vulnerable.
  • Apache Roller 6.1.5 is also affected by this same issue, despite the earlier narrower listing in CVE-2026-82384.
  • Apache Roller 6.1.6 and later are the recommended safe versions.

Resolution Guide

Preferred fix: upgrade Roller. If you deploy from source, package, or container, update the application artifact to 6.1.6+ and redeploy.

# Example: update your deployment artifact to the fixed release
# TODO: replace with your exact Roller distribution or image tag
curl -LO https://downloads.apache.org/roller/6.1.6/apache-roller-6.1.6.zip
unzip apache-roller-6.1.6.zip
# redeploy according to your environment

Emergency hardening if you cannot upgrade immediately:

<!-- WEB-INF/web.xml -->
<context-param>
  <param-name>enabledForExtensions</param-name>
  <param-value>false</param-value>
</context-param>

<!-- Or remove this servlet mapping entirely -->
<!--
<servlet-mapping>
  <servlet-name>xmlrpc</servlet-name>
  <url-pattern>/roller-services/xmlrpc</url-pattern>
</servlet-mapping>
-->
# Restart Roller after config changes
systemctl restart tomcat
# or
docker restart roller

Container guidance: if you use Docker, move to the fixed tag only after verifying the image includes Roller 6.1.6 or later.

# TODO: replace with your actual image name
docker pull your-registry/roller:6.1.6
docker run --rm your-registry/roller:6.1.6

Package manager notes: Roller is typically not installed via npm, pip, or apt/yum as a library. If your team repackages it into a platform artifact, update the Roller release itself rather than a language dependency.

# Java build systems: update the application dependency or distribution reference
# Maven/Gradle examples are placeholders if you vendor Roller as a dependency
# TODO: set the correct artifact coordinates if applicable

# Maven
mvn -DskipTests package

# Gradle
./gradlew build

Minimal code/config fix example: ensure XML-RPC is disabled at startup and the servlet mapping is absent when not needed.

// Pseudocode / configuration pattern
if (!xmlRpcEnabled) {
    disableServletMapping("/roller-services/xmlrpc");
    setConfig("enabledForExtensions", "false");
}

Detection & Verification

Check the installed version:

# From the deployed app or release metadata
grep -R "roller" /path/to/roller/WEB-INF/lib 2>/dev/null
# or inspect the app version in the admin/about page if accessible

Check for the vulnerable XML-RPC endpoint:

grep -R "/roller-services/xmlrpc" /path/to/roller/WEB-INF/web.xml
grep -R "enabledForExtensions" /path/to/roller/WEB-INF/web.xml

Verify the fix:

# The endpoint should return an error or be unreachable after mitigation
curl -i https://your-site.example/roller-services/xmlrpc

# Confirm the config value is false
grep -n "enabledForExtensions" /path/to/roller/WEB-INF/web.xml

Dependency / artifact checks: if your deployment pipeline tracks release manifests, confirm the deployed artifact is 6.1.6+ and that no older Roller WAR is cached in your build or container registry.

Risk and Impact

This flaw can give an attacker full remote code execution without a login, which means they may be able to read data, modify posts, steal credentials, or pivot deeper into your network. For small teams, the blast radius can include the entire blog server, attached databases, secrets in environment variables, and any internal systems reachable from that host.

Because exploitation happens through a public-facing XML-RPC endpoint, exposure is highest when Roller is internet-accessible. If your instance is public and running a vulnerable version, assume it is at immediate risk and act now.

Keep reading