1. Basic Information
- Article Name: CVE-2026-129448: Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)
- Source: Apache Software Foundation
- Publication Date: November 17, 2026
- Original: Apache Software Foundation Mailing List
- Related Sources: Apache Advisory (republished by oss-security), BleepingComputer
- Related CVEs: CVE-2026-129448, CVE-2026-82384
- Affected Products: Apache Roller 4.0.0 to 6.1.4 (CVE-2026-129448), 6.1.5 (CVE-2026-82384 for the same flaw)
- Severity: Critical (Author Priority)
- Official Rating: Apache rates the severity as Critical with a CVSS v3.1 score of 9.8.
2. Quick Summary
The XML-RPC endpoint deserializes vendor extension types before authentication, allowing remote attackers to execute arbitrary code. Apache has confirmed active exploitation.
3. Attack Flow
The following paths divide the same flaw by target version and CVE, rather than representing a continuous attack sequence. These paths describe how exploitation works according to the Apache advisory; the attack steps used in individual incidents have not been disclosed.
Path A: CVE-2026-129448 (Versions 4.0.0 to 6.1.4)
- An attacker sends a crafted request to
/roller-services/xmlrpc. - Vendor extension types are deserialized prior to authentication and feature-disablement checks.
- If exploitation succeeds, arbitrary code may be executed with the privileges of the Roller process.
Path B: CVE-2026-82384 (Version 6.1.5)
- An attacker sends a crafted request to the same XML-RPC endpoint in version 6.1.5.
- Due to the same pre-authentication deserialization flaw, successful exploitation may lead to arbitrary code execution with the privileges of the Roller process.
4. Attacker Position and Execution Location
A remote attacker on the internet without credentials. Code executes on the JVM and application server running Roller.
5. Perspective of Victims and Administrators
Inference: The following outlines expected signs during an investigation and does not represent published observations from a victim environment. These depend on log collection and monitoring configurations.
Users may experience blog service anomalies or outages. Administrators may observe POST requests to XML-RPC, JVM child process creation, unexpected outbound connections, or changes to the web root.
6. Success and Failure Conditions
Exploitation requires reachability to the XML-RPC servlet in versions 4.0.0 to 6.1.4 for CVE-2026-129448, and in version 6.1.5 for CVE-2026-82384 (which involves the same flaw). Disabling XML-RPC in the management console is insufficient. Update to version 6.1.6 or later. If an immediate update is not possible, set enabledForExtensions=false in WEB-INF/web.xml or remove the servlet mapping for /roller-services/xmlrpc, and restart Roller in either case.
7. What Happens Upon Success
Arbitrary code execution with the privileges of the Roller process can lead to content tampering, credential theft, and the introduction of follow-up tools. Attackers, payloads, and the scale of compromise remain unpublicized.
8. Observable Logs
Inference: The following are candidate log sources and artifacts for investigation. They depend on collection settings, permissions, and retention periods; the absence of logs does not prove the absence of a compromise.
- Proxy/SWG/DNS: Unusual POST requests to the XML-RPC endpoint
- Endpoint/EDR: Initiation of shells, download tools, or script interpreters from the JVM
- Identity/IdP: Requests not accompanied by successful logins
- Network: Connections from the Roller server to new destinations
9. Attack Success Determination
Confirmed in Public Information
While Apache has disclosed active exploitation of this vulnerability, it has not provided details of compromises, payloads, or stages of successful exploitation for each CVE or affected version. This does not confirm initial execution for either Path A or Path B, nor does it imply that all public servers have been compromised.
Internal Evaluation Criteria
- Path A (CVE-2026-129448): Treat XML-RPC requests alone as an attempt. Confirm initial execution only when evidence substantiates attacker-specified code execution causally linked to the request.
- Path B (CVE-2026-82384): Apply the same criteria to version 6.1.5. Do not conclude compromise based solely on JVM child process creation or file creation; establish how the activity differs from legitimate processing and how it relates to exploitation.
For both paths, credential theft and persistent access require additional evidence to confirm follow-up compromise.
10. Investigation Playbook
- Verify the software version, public exposure status of XML-RPC, and reverse proxy logs.
- Search for POST requests to the endpoint and JVM child process creation.
- Preserve information regarding the web root, plugins, startup configurations, credentials, and outbound connections.
- Update to version 6.1.6 or later, and block access to the XML-RPC endpoint as necessary.
- If execution artifacts are found, perform system rebuilding and credential rotation.
11. Defense and Detection Ideas
Do not expose unnecessary XML-RPC endpoints to the internet. Detect attacks by correlating WAF request logs with JVM child process creation, file writes, and outbound traffic.
12. Facts / Inference / Hypothesis
- Fact: Versions 4.0.0 through 6.1.4 are affected, and the issue is fixed in 6.1.6 and later.
- Fact: The issue involves unauthenticated vendor extension type deserialization and is actively exploited.
- Inference: Internet-facing Roller instances may become targets, but the scale is unpublicized.
- Hypothesis: None.
13. MITRE ATT&CK Mapping
| ID | Technique | Confidence | Basis |
|---|---|---|---|
| T1190 | Exploit Public-Facing Application | High | Unauthenticated deserialization in the public XML-RPC endpoint. |
T1059 is not assigned because the possibility of RCE alone does not substantiate the use of commands or script interpreters, and payloads remain unpublicized.
14. Unknowns and Additional Research
The identity of the attackers, request patterns, payloads, number of victim organizations, and the actual exploitation scope and success stages per CVE remain unknown. Apache explained that CVE-2026-82384 shares the exact same flaw as this vulnerability, with that specific CVE targeting version 6.1.5 only.
15. Impact on SOCs and Organizations
Blog platforms that escaped administrative oversight may remain exposed to the internet. Check for the presence of XML-RPC endpoints from the external attack surface and investigate compromise artifacts even after updating.
16. Summary by Role
- SOC: Correlate XML-RPC POST requests with JVM child process creation, file writes, and outbound traffic.
- Administrators: Update to version 6.1.6 or later and remove unnecessary XML-RPC servlets.
- Users: Report blog service anomalies or unexpected changes to administrators.
Top comments (0)