The Apache Software Foundation disclosed CVE-2026-129448 on November 17, an unauthenticated Java deserialization flaw in the Apache Roller blog server’s XML-RPC endpoint, and said in the advisory that “this issue is being actively exploited.” It is rated CVSS 9.8, affects every Roller release from 4.0.0 through 6.1.4, and a public PoC and scanner are already on GitHub.

The bug isn’t new. It is the same root cause as CVE-2026-82384, disclosed in late September for Roller 6.1.5 only. The new CVE extends that range back to 4.0.0. If you checked your Roller version in September, saw you weren’t on 6.1.5, and moved on, you were probably exposed the whole time.

Technical details

Roller exposes a MetaWeblog/Blogger API through an Apache XML-RPC servlet mapped at /roller-services/xmlrpc. That servlet was configured with Apache XML-RPC vendor extensions enabled (enabledForExtensions=true in WEB-INF/web.xml). With extensions on, the XML-RPC parser accepts the ex:serializable type, a base64-encoded Java serialized object that the library passes straight to ObjectInputStream.readObject().

Deserialization runs while the request body is parsed, before the request reaches any Roller handler. So it also runs:

  • before authentication, so no credentials are needed;
  • before Roller checks whether the XML-RPC feature is enabled at all.

Turning off “Enable Weblog Client API” in the admin UI therefore does not protect you on affected versions. The servlet still parses and deserializes the body before it reads that setting. Code execution then needs only a usable gadget chain on the classpath, and a typical Roller WAR deployment (Spring, Commons libraries, the servlet container’s own jars) gives an attacker several to try.

The attack is a single HTTP POST with Content-Type: text/xml to /roller-services/xmlrpc, carrying a <methodCall> whose parameter is an <ex:serializable> blob. Code runs as the servlet container’s user, usually the Tomcat service account, which normally has read access to Roller’s database credentials in roller-custom.properties and the JNDI datasource config.

Exploitation and impact

Apache has not named the actors or the number of compromised instances, and as of this writing CISA has not added the CVE to KEV. Roller is a niche product. It turns up mostly in long-lived corporate, university, and open-source project blogs, often on Tomcat hosts that nobody has patched in years and that sit on internal networks with a public reverse proxy in front. Those are exactly the hosts nobody is watching, and they make a useful foothold: a Java app server with database credentials, inside the perimeter.

With a public PoC and a vendor-confirmed exploitation statement, expect mass scanning of /roller-services/xmlrpc if it isn’t already happening.

Affected and fixed versions

CVEAffectedFixed
CVE-2026-129448Roller 4.0.0 – 6.1.46.1.6+
CVE-2026-82384Roller 6.1.56.1.6+

Roller 6.1.6 disables the XML-RPC extension types and rejects XML-RPC requests outright when the feature is turned off. Go straight to 6.1.7, released November 11. It fixes a separate batch of roughly 15 CVEs, and those advisories list 6.1.6 as affected.

What to do now

  1. Find every Roller instance. Search for roller.war, roller-custom.properties, and HTTP responses from /roller-services/xmlrpc or /roller-ui/. Old departmental blogs are the usual blind spot.
  2. Upgrade to 6.1.7.
  3. If you can’t upgrade today, set enabledForExtensions to false for the XML-RPC servlet in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping entirely, then restart. Also block the path at the reverse proxy or WAF. Most deployments don’t use desktop blogging clients and lose nothing.
  4. Hunt for compromise. Check access logs for POSTs to /roller-services/xmlrpc, especially large bodies or unfamiliar user agents. Look at the container user for unexpected child processes (sh, bash, curl, wget, powershell), new JSP files under the webapp directory, and outbound connections from the Tomcat JVM.
  5. Assume credential exposure on any hit. Rotate the Roller database password and any secrets readable by the service account, and review the database for added admin users.

References