Vulnerabilities · Application Security
Critical Apache Roller flaw lets attackers run code without logging in
A serious vulnerability in Apache Roller is being actively exploited. Attackers can run code on affected servers without needing to log in, and urgent updates are advised.
Ross Grant2 min read

The short version
A serious bug in Apache Roller, a blogging platform, lets attackers take control of servers without needing a password. The problem affects many versions and is already being used by attackers. The makers of Apache Roller say to update right away or use a workaround if you can't. If you run this software, check your version and act quickly.
What happened?
A critical vulnerability in Apache Roller, tracked as CVE-2026-129448, is being actively exploited. Attackers can run code on affected servers without needing to log in. The flaw affects versions 4.0.0 through 6.1.4 and is found in the XML-RPC endpoint. The Apache Software Foundation recommends urgent updates or workarounds.
How the flaw works
A critical security flaw has been found in Apache Roller, an open-source blogging platform written in Java. The vulnerability, tracked as CVE-2026-129448, has a CVSS score of 9.8, which means it is considered very serious. Attackers can exploit this flaw to run any code they want on a vulnerable server, and they do not need to log in first. This is known as remote code execution (RCE) without authentication.
The problem is in the XML-RPC endpoint, which is a part of the software that lets other programs communicate with Apache Roller. The endpoint processes certain types of data (called vendor extension types) before checking if the request is from a trusted source. This means an attacker can send specially crafted data to the server and have it processed, even if they are not logged in. The flaw is a case of deserialization of untrusted data, which is a common way attackers gain control over applications (The Hacker News (opens in a new tab), Security Affairs (opens in a new tab)).
Who is affected
The affected versions are Apache Roller 4.0.0 through 6.1.4. The project had previously warned only about version 6.1.5, but the latest advisory expands the risk to a much wider range. Any organisation running these versions is at risk, especially if their server is accessible from the internet. However, even servers that are only reachable inside a company network can be targeted if an attacker gets access to the internal network.
The response
The Apache Software Foundation has confirmed that attackers are already exploiting this flaw. They recommend upgrading to Apache Roller 6.1.6 or later, which fixes the problem by disabling the risky feature and rejecting unsafe requests. If you cannot upgrade right away, there are workarounds: you can set "enabledForExtensions" to "false" in the configuration file (WEB-INF/web.xml), or remove the mapping for the XML-RPC servlet. In both cases, you must restart the server for the change to take effect. Simply turning off XML-RPC in the admin interface does not fix the problem in older versions, because the vulnerable code runs before that setting is checked (Security Affairs (opens in a new tab)).
What you should do
If you run Apache Roller, check which version you have and whether the XML-RPC endpoint is accessible. Upgrade to 6.1.6 or later as soon as possible. If you cannot upgrade, apply one of the recommended workarounds and restart your server. Pay special attention to any systems that are exposed to the internet, but do not ignore internal servers. Attackers can use any vulnerable system as a stepping stone if they get into your network.
Why it matters
Remote code execution flaws are among the most dangerous because they let attackers take over servers. This bug affects a popular open-source tool and is already being used in real attacks. Organisations that use Apache Roller need to act fast to protect their systems.
Key points
- Critical Apache Roller flaw allows unauthenticated remote code execution.
- Versions 4.0.0 through 6.1.4 are affected, not just the latest.
- Attackers are already exploiting this vulnerability in the wild.
- Upgrading to version 6.1.6 or later is the recommended fix.
- Workarounds exist but require careful configuration and a server restart.
Sources
The Hacker News
Reference
Security Affairs
Reference


