CVE-2026-82384: Apache Roller XML-RPC Java Deserialization Pre-Auth Remote Code Execution
HERMES THREAT SCORE & WEB CMS EXPOSURE
Target:Apache Roller Weblog Server - XML-RPC Endpoint (/roller-services/xmlrpc) Standard CVSS v3.1 rates CVE-2026-82384 at 9.8 (Critical, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The Hermes Threat Score assigns an operational score of 95 (CRITICAL). Apache Roller powers mission-critical public blogs, developer publications, and enterprise knowledge intranets, including the official Apache Software Foundation blogs. Because the XML-RPC servlet is mapped unconditionally by default in web.xml and deserialization occurs during preliminary XML-RPC unmarshalling prior to any authentication checks or feature-flag verifications, remote adversaries can weaponize known Java gadget chains (e.g., CommonsCollections, Spring) to attain instant remote shell access on the underlying Java application server.
CVE-2026-82384: Apache Roller XML-RPC Java Deserialization Pre-Auth Remote Code ExecutionVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Apache Roller Weblog Server documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโApache Roller is an enterprise-class Java weblog server and CMS designed for multi-user, multi-blog platforms, widely utilized in enterprise intranets and open-source foundations.
| Parameter | Technical Specification | Operational Impact |
|---|---|---|
| CVE Identifier | CVE-2026-82384 | Global vulnerability tracking reference |
| Vendor Advisory | ASF Security Advisory (September 2026) | Apache Roller security disclosure |
| Vulnerability Class | Deserialization of Untrusted Data (CWE-502) | Pre-authentication remote code execution |
| Vulnerable Component | /roller-services/xmlrpc (RollerXmlRpcServlet) | Apache XML-RPC 3.x request parser |
| Affected Releases | Apache Roller <= 6.1.5 | Standard web archive (WAR) deployments |
| Fixed Release | 6.1.6 | Disabled vendor extensions & strict request rejection |
| Attack Vector | Network, Unauthenticated, Zero Preconditions | Single HTTP POST request to exposed endpoint |
2. In-Depth Technical Decomposition
Section titled โ2. In-Depth Technical DecompositionโApache Roller XML-RPC Architecture
Section titled โApache Roller XML-RPC ArchitectureโApache Roller implements standard Blogger, MetaWeblog, and MovableType APIs via XML-RPC. In versions up to 6.1.5, the web deployment descriptor (web.xml) unconditionally routes incoming requests for /roller-services/xmlrpc to RollerXmlRpcServlet:
UNAUTHENTICATED ATTACKER (Internet) โ โ HTTP POST /roller-services/xmlrpc โ Content-Type: text/xml (Payload with <serializable>) โผ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ Apache Tomcat / Jetty โ โ Servlet Container โ โโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโ โ Matched URL Pattern in web.xml โผ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ RollerXmlRpcServlet โ โ (Apache XML-RPC Engine) โ โโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโ โ Request Parsing: TypeFactory & ObjectInputStream โผ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ Deserialization Sink โ <--- [CVE-2026-82384 Vulnerability] โ ObjectInputStream.read() โ Attacker-controlled byte array โโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโ โ Gadget Chain Invocation (Commons / Spring) โผ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ Arbitrary Code Execution โ โ (Tomcat process context) โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโRoot Cause Analysis: The <serializable> Extension Sink
Section titled โRoot Cause Analysis: The <serializable> Extension SinkโApache XML-RPC allows vendor extensions that support passing custom Java objects serialized as Base64 strings. When the XML-RPC parser encounters a <serializable> element, it decodes the payload and instantiates an ObjectInputStream:
<?xml version="1.0"?><methodCall> <methodName>blogger.getUsersBlogs</methodName> <params> <param> <value> <serializable xmlns="http://ws.apache.org/xmlrpc/namespaces/extensions"> rO0ABXNyABFqYXZhLnV0aWwuSGFzaE1hcAUH2sBFlme0AwAC... [Base64 Serialized Gadget Chain] </serializable> </value> </param> </params></methodCall>In RollerXmlRpcServlet, the server configuration permitted extension types by default. Furthermore, request unmarshalling occurs immediately inside XmlRpcHttpServer.execute() before invoking Rollerโs authentication interceptors:
// Vulnerable request handling flow in Roller XML-RPC parserpublic class RollerXmlRpcServlet extends HttpServlet { protected void doPost(HttpServletRequest req, HttpServletResponse resp) { // VULNERABILITY 1: No verification of global XML-RPC toggle in roller.properties // VULNERABILITY 2: Extensions enabled without class filtering or JEP 290 filters XmlRpcServletServer server = new XmlRpcServletServer(); XmlRpcServerConfigImpl config = (XmlRpcServerConfigImpl) server.getConfig(); config.setEnabledForExtensions(true); // Permits <serializable> objects
// SINK: Body unmarshalling invokes ObjectInputStream.readObject() before auth server.execute(req, resp); }}Because the servlet container classpath includes libraries commonly used by Roller (such as Apache Commons Collections or Spring dependencies), an attacker can supply pre-computed gadget chains generated with tools like ysoserial to trigger command execution upon deserialization.
3. Attack Vectors & Real-World Exploitation Chain
Section titled โ3. Attack Vectors & Real-World Exploitation ChainโsequenceDiagram autonumber participant Attacker as Unauthenticated Remote Adversary participant Web as Web Server (Tomcat / Roller) participant Servlet as RollerXmlRpcServlet participant JVM as JVM Execution Engine
Attacker->>Web: POST /roller-services/xmlrpc Note over Attacker,Web: Body contains <serializable> base64 gadget payload Web->>Servlet: Dispatch request to RollerXmlRpcServlet Servlet->>Servlet: Parse XML-RPC XML document Servlet->>Servlet: Decode base64 <serializable> byte stream Servlet->>JVM: Invoke ObjectInputStream.readObject() JVM->>JVM: Execute dynamic gadget chain (e.g., CommonsCollections / Runtime.exec) JVM-->>Attacker: Spawn reverse shell / write JSP webshell to /roller/- Endpoint Probing: The attacker issues a lightweight XML-RPC ping or
system.listMethodscall to/roller-services/xmlrpcto verify responsiveness. - Payload Generation: A Java deserialization gadget payload is formatted into an XML-RPC
<methodCall>enclosing a Base64-encoded serialized object. - Pre-Auth Delivery: The HTTP POST request is submitted to the application server. The servlet unmarshals the object before verifying user credentials or checking whether XML-RPC is disabled in the administrative settings.
- Execution & Web Shell Drop: The gadget chain triggers
Runtime.getRuntime().exec(), launching a shell command that drops a persistent JSP webshell into the webroot, granting full system access under thetomcatservice account.
4. Forensic Triage & Detection Engineering
Section titled โ4. Forensic Triage & Detection Engineeringโtitle: Apache Roller XML-RPC Java Deserialization Attemptid: c7e19320-8238-4a61-912f-823840000001status: experimentaldescription: Detects HTTP POST requests to Apache Roller XML-RPC endpoint containing Java serialization markers or vendor extension tags.references: - https://lists.apache.org/thread/roller-security-cve-2026-82384 - https://nvd.nist.gov/vuln/detail/CVE-2026-82384author: Hermes Codex Cyber Intelligencedate: 2026-09-29logsource: category: webserverdetection: selection_endpoint: cs-method: "POST" cs-uri-stem|contains: "/roller-services/xmlrpc" selection_payload: cs-body|contains: - "<serializable" - "rO0AB" - "ws.apache.org/xmlrpc/namespaces/extensions" condition: selection_endpoint and selection_payloadfalsepositives: - None expected in standard production environmentslevel: criticaltags: - attack.initial_access - attack.t1190 - attack.execution - attack.t1059// Azure Sentinel / WAF / IIS / Tomcat Web Access Logs// Identify suspicious XML-RPC invocation targeting Apache RollerW3CIISLog| where csMethod == "POST" and csUriStem has "/roller-services/xmlrpc"| where csUserAgent !has "Pingback"| extend HasSerializable = csBytes > 1500| project TimeGenerated, cIP, csMethod, csUriStem, scStatus, csBytes, csUserAgent| sort by TimeGenerated desc#!/bin/bash# Emergency audit script for Apache Roller access logs
echo "=== 1. Checking access logs for POST requests to XML-RPC endpoint ==="grep -E "POST .*/roller-services/xmlrpc" /var/log/tomcat*/localhost_access_log*.txt 2>/dev/null | tail -n 30
echo "=== 2. Inspecting webapps directory for unexpected JSP files ==="find /var/lib/tomcat*/webapps/roller/ -type f -name "*.jsp" -mtime -7 -ls
echo "=== 3. Checking for suspicious outbound connections from Tomcat ==="netstat -antp | grep java | grep ESTABLISHEDalert http any any -> any any ( msg:"HERMES - Apache Roller XML-RPC Java Deserialization Attempt (CVE-2026-82384)"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/roller-services/xmlrpc"; http.request_body; content:"<serializable"; nocase; http.request_body; content:"rO0AB"; classtype:web-application-attack; sid:202682384; rev:1;)5. Remediation Strategy & Mitigation Controls
Section titled โ5. Remediation Strategy & Mitigation Controlsโ-
Upgrade to Apache Roller 6.1.6:
Deploy the official Apache Roller 6.1.6 release. This version explicitly disables vendor extension handling inRollerXmlRpcServletand enforces rejection of requests if XML-RPC is disabled inroller.properties. -
Immediate Workaround (Disable Endpoint in
web.xml):
If updating the WAR file cannot be executed immediately, comment out or remove the servlet mapping inWEB-INF/web.xml:<!-- Remove or comment out this mapping --><!--<servlet-mapping><servlet-name>RollerXmlRpcServlet</servlet-name><url-pattern>/roller-services/xmlrpc</url-pattern></servlet-mapping>-->Restart the Tomcat or application container to apply changes.
-
Deploy JVM Serialization Filtering (JEP 290):
Configure JVM-level object input filters inCATALINA_OPTS:Terminal window CATALINA_OPTS="$CATALINA_OPTS -Djdk.serialFilter=!*;\java.lang.*;java.util.*;maxdepth=10;maxbytes=100000"This prevents arbitrary classes from being instantiated during any untrusted deserialization.