Security Digest · Nov 17, 2026 · Vulnerability · Other
Apache Roller CVE-2026-129448: Exploited XML-RPC RCE
Unauthenticated RCE via Apache Roller's XML-RPC endpoint in 4.0.0-6.1.5, exploited and in CISA KEV. Upgrade to 6.1.6+ (6.1.7 current) today.
Our verdict
Act now
If you run Apache Roller, upgrade or disable the XML-RPC extension setting today: one unauthenticated POST runs code, Apache says attacks are under way, and September's advisory understated which versions were vulnerable.
Who must act: Anyone running Apache Roller 4.0.0 through 6.1.5, especially instances reachable from the internet, including sites that turned XML-RPC off in the admin UI.
Who can relax: Organizations that do not run Apache Roller and instances already on 6.1.6 or 6.1.7 that show no signs of earlier compromise.
- Affected
- Apache Roller 4.0.0 through 6.1.4 (CVE-2026-129448)
Apache Roller 6.1.5 (CVE-2026-82384) - Fixed in
- Apache Roller 6.1.6
Apache Roller 6.1.7 (current best available release) - CVSS
- 9.8 (v3.1, CNA)
- EPSS
- 5.5% (percentile 93)
- CISA KEV
- Yes, listed as known exploited
- Exploitation
- Exploited in the wild
- Severity
- Critical
What to do
- Upgrade every Apache Roller instance to 6.1.7 (6.1.6 at minimum) and restart the servlet container.
- If you cannot upgrade today, set enabledForExtensions to false on XmlRpcServlet in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart; the admin UI toggle is not enough.
- Block /roller-services/xmlrpc at the reverse proxy or WAF unless you rely on XML-RPC blogging clients.
- Inventory instances and versions: grep ro.version webapps/roller/WEB-INF/classes/roller-version.properties on each servlet container.
- Hunt for compromise before closing the ticket, and rotate the database and mail credentials Roller uses if you find any.
How to check if you are affected or compromised
- Search reverse proxy and Tomcat access logs for POST /roller-services/xmlrpc from clients you do not recognize.
- If request bodies are logged, look for ex:serializable or the namespace http://ws.apache.org/xmlrpc/namespaces/extensions.
- Look in EDR or process logs for sh, bash, curl or wget started by the Java process that runs Roller.
- Check the Roller webapp and container work directories for new JSP or class files, and Roller for user accounts you did not create.
What happened#
On November 17, 2026, the Apache Roller project published CVE-2026-129448, an unauthenticated remote code execution flaw in the XML-RPC endpoint of its Java blog server. The advisory, also posted to oss-security, says the endpoint "accepts vendor extension types and deserializes them before authenticating the requester." It also states: "This issue is being actively exploited." The project rates the flaw critical, with a CVSS 3.1 score of 9.8.
The bug itself is not new. In September the project disclosed it as CVE-2026-82384, but that advisory listed only Roller 6.1.5 as affected. The new CVE extends the range back to 4.0.0. On November 20, CISA added CVE-2026-129448 to the Known Exploited Vulnerabilities catalog and gave federal agencies a deadline of November 23.
Why the endpoint is dangerous#
Roller serves its XML-RPC blogging API through the Apache XML-RPC library's XmlRpcServlet, mapped to /roller-services/xmlrpc. The WEB-INF/web.xml that ships with Roller 6.1.5 sets the servlet's enabledForExtensions parameter to true. The library's type documentation lists an ex:serializable extension type, described as a Java object "converted into a serialized representation and transmitted as a base 64 encoded byte array." Turning extensions on means that Java deserialization runs on bytes from the request before Roller checks a username or password. Apache says the result is arbitrary code execution by an unauthenticated remote attacker.
Who is affected#
Every Apache Roller release from 4.0.0 through 6.1.5 is affected. CVE-2026-129448 covers 4.0.0 through 6.1.4, and CVE-2026-82384 covers 6.1.5. The fix is Roller 6.1.6 or later. The advisory says 6.1.6 "disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled." The change is pull request #171, merged on September 5. It turns extensions off and adds a filter that closes the endpoint whenever XML-RPC is disabled. The project's downloads page lists 6.1.7 as the "best available" release.
The problem is how Roller configures the library, so other applications are not affected by this CVE. Still, any Java service that sets enabledForExtensions to true on an endpoint untrusted clients can reach takes the same kind of risk.
Do you really need to act?#
If you run Roller, yes, today. The attack needs no account and no user interaction, and the target is a fixed, well-known URL. The attacker sends one HTTP POST, and the payload runs as whatever user runs your servlet container. Apache says exploitation is under way. It has not said who is behind it or how many servers have been hit, BleepingComputer reports.
Two details make it easy to believe you are safe when you are not. First, admins on 6.1.4 or older who read the September advisory were told they were not affected. They were, and the fix has been available since 6.1.6. Second, the advisory warns that "Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting." A site that turned the feature off in the UI is still exposed.
Everyone else can relax. Roller is a niche product, and most organizations have never deployed it. The quickest check is whether any servlet container you run has a roller webapp.
What to do now#
- Find instances and versions. For Tomcat, run
ls $CATALINA_BASE/webapps/and thengrep ro.version $CATALINA_BASE/webapps/roller/WEB-INF/classes/roller-version.properties. Adjust the path if you deployed under a different context name. - Upgrade to Roller 6.1.7, or 6.1.6 at minimum. Read the 6.1.7 release notes first, because the project flags behavior changes for live sites.
- If you cannot upgrade today, edit
WEB-INF/web.xml. Change theenabledForExtensionsinit-param ofXmlRpcServlettofalse, or delete theservlet-mappingfor/roller-services/xmlrpc. Restart the container afterwards. Do not rely on the admin UI switch. - Unless you depend on XML-RPC blogging clients, block the path at the edge as well. For nginx:
location = /roller-services/xmlrpc { return 403; } - Check for compromise before you close the ticket. A patch does not remove a webshell that was planted before it.
How to tell if you were hit#
Search your access logs for requests to the endpoint, for example grep -h "POST /roller-services/xmlrpc" /var/log/nginx/access.log* $CATALINA_BASE/logs/localhost_access_log*. Legitimate requests should come only from blogging clients you know about. If your proxy or WAF records request bodies, search them for ex:serializable or the extensions namespace http://ws.apache.org/xmlrpc/namespaces/extensions. Normal Roller clients do not send either.
On the host, look for sh, bash, curl or wget started by the Java process. Also look for new JSP or class files in the webapp and container work directories, and for Roller accounts you did not create. If you find any of these, treat the host as compromised. Rotate the database and mail credentials in Roller's configuration, and rebuild from a known-good image rather than cleaning in place.
Timeline#
- — The fix that disables XML-RPC extension types (PR #171) is merged.
- — Roller 6.1.6 is tagged with the fix.
- — Apache announces CVE-2026-82384, listing only Roller 6.1.5 as affected.
- — Roller 6.1.7 is tagged.
- — CVE-2026-129448 extends the affected range to 4.0.0 through 6.1.4, and Apache says the flaw is being actively exploited.
- — CISA adds CVE-2026-129448 to the KEV catalog, with a federal deadline of November 23.
Vulnerability records
- CVE-2026-129448 · KEV 2026-11-20 · Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code.
- CVE-2026-82384 · Deserialization of Untrusted Data in Apache Roller 6.1.5 allows an unauthenticated remote attacker to cause deserialization of attacker-controlled bytes…
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- Apache Roller — CVE-2026-129448: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5) lists.apache.org
- CVE record — CVE-2026-129448 (Apache Software Foundation) cve.org
- oss-security — CVE-2026-129448: Apache Roller (Nov 17, 2026) openwall.com
- Apache Roller — CVE-2026-82384: Unauthenticated deserialization in the XML-RPC endpoint (Sep 2026) lists.apache.org
- CVE record — CVE-2026-82384 (Apache Software Foundation) cve.org
- apache/roller — PR #171: Disable vendor extension types on the XML-RPC servlet github.com
- Apache Roller — Downloads roller.apache.org
- Apache XML-RPC — Data Types ws.apache.org
- CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 20, 2026) cisa.gov
- CISA — Known Exploited Vulnerabilities catalog entry for CVE-2026-129448 cisa.gov
Coverage and analysis
- BleepingComputer — Apache warns of Roller RCE vulnerability exploited in attacks bleepingcomputer.com