Security alerts · November 19, 2026

Apache Roller flaw lets attackers run code on servers without logging in, now exploited

Apache warns that CVE-2026-129448 in the Apache Roller blogging platform is being actively exploited. Attackers can run their own code on the server through the XML-RPC interface without logging in. Upgrade to 6.1.6. Disabling XML-RPC in the admin UI is not enough.

Updates

November 20, 2026: On November 20, 2026, CVE-2026-129448 was added to the CISA KEV catalog, which means attackers are now actively exploiting it. If you have not updated yet, make it a priority.

What happened

On November 17, 2026, the Apache Software Foundation (ASF) disclosed CVE-2026-129448, a critical vulnerability in Apache Roller, its open-source, Java-based blogging platform. The flaw sits in the XML-RPC interface, which lets people publish to the blog from external programs. Through it, an attacker can run their own code on the server without logging in.

Apache says this is the same flaw already tracked as CVE-2026-82384. According to The Hacker News, that issue was patched in September 2026, but its record listed only version 6.1.5 as affected. The new record adds the older versions 4.0.0 through 6.1.4.

Apache states explicitly that the issue is being actively exploited. According to The Hacker News, the ASF has not shared how the attacks work or who is being targeted. The Hacker News credits researcher n0mi1k with finding the flaw and Matt Raible with reporting it.

Why it is dangerous

This type of flaw is called deserialization of untrusted data (CWE-502). A program receives a packed data object over the network and “unpacks” it back into a form it can work with. If it does not properly check what it is unpacking and who sent it, an attacker can slip in an object that runs their commands during unpacking.

Picture a mailroom that opens every parcel and assembles whatever is inside by following the enclosed instructions, and only then checks who sent it. That is how Roller’s XML-RPC interface behaves: according to Apache, it accepts extended data types and unpacks them before verifying who sent the request.

That is why the attacker needs no password or account, only network access to the server, typically over the internet. They can then run arbitrary code with the permissions Roller runs under. In practice, that can mean access to blog content, the database and stored credentials, and a foothold for moving deeper into the company network.

  • CVSS 9.8 out of 10: a severity score assigned by the Apache Software Foundation itself, using CVSS 3.1. It means a critical flaw that can be exploited remotely, easily and without logging in.
  • EPSS 1.64% (as of November 18, 2026): an estimate of the probability that the flaw will be exploited in the next 30 days. It looks low, but it is higher than for roughly 77% of known vulnerabilities. For a flaw the vendor has already confirmed as exploited, it matters less than that confirmation.
  • CISA KEV: the U.S. agency CISA’s catalog of vulnerabilities known to be exploited. At the time of writing, this flaw was not listed. That does not change the fact that the vendor itself has confirmed attacks.

Who is affected

This affects anyone running their own Apache Roller instance on versions 4.0.0 through 6.1.4. Version 6.1.5 was listed as affected in the earlier record CVE-2026-82384 for the same flaw. According to Apache, you are safe only on version 6.1.6 or later.

Roller is a Java application that usually runs on an application server such as Apache Tomcat. You will typically find it behind company and organization blogs, intranet blogs, or older websites that someone set up years ago and nobody has looked after since. The risk is highest where the blog is reachable from the internet.

Important: having XML-RPC turned off in Roller’s admin UI is not enough. According to Apache, older versions unpack the request before they check that setting. If you do not run Apache Roller at all, this flaw does not affect you.

How to check if you are affected

First find out whether Roller is deployed on the server and under what name. The paths below are examples for Tomcat, so adjust them to your server. All commands only read data and change nothing.

ls -l /opt/tomcat/webapps/

If the application was built with Maven, the version is in the pom.properties file inside the application:

find /opt/tomcat/webapps -name pom.properties -path '*roller*' -exec cat {} \;

Also check whether the XML-RPC interface is enabled in the application configuration file WEB-INF/web.xml:

grep -n -A2 -e enabledForExtensions -e roller-services/xmlrpc /opt/tomcat/webapps/roller/WEB-INF/web.xml

If your version is older than 6.1.6, web.xml contains the /roller-services/xmlrpc mapping and enabledForExtensions is not set to false, treat the server as vulnerable. Even with the workaround in place, plan the upgrade.

How to fix it

Apache recommends upgrading to Apache Roller 6.1.6 or later. That version disables the problematic extension types and rejects XML-RPC requests when the XML-RPC feature is turned off.

  • List every server running Roller, including test systems and forgotten instances.
  • If you cannot upgrade right away, apply the temporary workaround below first. Do not delay this on internet-facing servers.
  • Back up the database, configuration and application directory.
  • Deploy version 6.1.6 or later following the project documentation and restart the application server.
  • Confirm the version using the commands in the previous section and check that the blog works.
  • Check whether the server was compromised. Upgrading does not remove anything an attacker may already have left behind.

Apache’s temporary workaround: in WEB-INF/web.xml, set the enabledForExtensions parameter to false, or remove the /roller-services/xmlrpc servlet mapping entirely. Then restart Roller. Turning XML-RPC off in the admin UI alone is not enough.

If you do not use XML-RPC, for example to publish from external blogging tools, removing the mapping costs you nothing. The workaround does not replace the upgrade, though, so finish that as soon as possible.

What if you may already be compromised

Apache has not yet published specific indicators of compromise, such as IP addresses or file names. Because the flaw is being actively exploited, assume that a vulnerable, internet-facing version may have been hit and check for it.

  • Web and application server access logs: requests to /roller-services/xmlrpc, especially from unknown addresses and if you do not normally use XML-RPC.
  • New or modified files in the application and application server directories, for example unfamiliar .jsp files.
  • Unknown processes, scheduled tasks or outbound connections under the account Roller runs as.
  • New user accounts in Roller and in the operating system.

To find XML-RPC requests in Tomcat’s access logs, including older compressed ones, run:

zgrep -h 'roller-services/xmlrpc' /opt/tomcat/logs/localhost_access_log* 2>/dev/null

If a reverse proxy sits in front of Tomcat, search its logs too. The second command lists .jsp files changed in the last 30 days:

zgrep -h 'roller-services/xmlrpc' /var/log/nginx/access.log* /var/log/apache2/access.log* /var/log/httpd/access_log* 2>/dev/null
find /opt/tomcat/webapps -name '*.jsp' -mtime -30 -ls

If you find anything suspicious, disconnect the server from the network, but do not shut it down or delete anything, so that evidence is preserved. Change the database password and other credentials stored on the server. Bring in an incident response specialist, especially if the server can reach your internal network.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.