> ## Content Index
> Fetch the complete content index at: https://stackurity.ai/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Apache Roller CVE-2026-129448 is exploited: upgrade to 6.1.6
- URL: https://stackurity.ai/blog/apache-roller-cve-2026-129448-exploited-xmlrpc-deserialization/
- Published: 2026-11-22T01:35:05.000Z
- Updated: 2026-11-22T01:35:04.000Z
- Description: Attackers exploit Apache Roller flaw CVE-2026-129448 to run code through XML-RPC with no login. See affected versions, the 6.1.6 fix and a workaround.
- Author: Stackurity Research Team
- Tags: Actively Exploited, #deep-dive

## TL;DR

- **What:** Apache Roller, the open-source blogging server, has a flaw in its XML-RPC endpoint, tracked as CVE-2026-129448\. It deserializes data sent by the caller before it checks who the caller is.
- **Impact:** an unauthenticated attacker on the network can run arbitrary code on the server that hosts Roller.
- **Severity:** a CVSS v3.1 score of 9.8 (critical) from security@apache.org.
- **Exploited:** yes. CISA added it to the Known Exploited Vulnerabilities catalogue on November 20, 2026, and set a due date of November 23, 2026.
- **Fix:** move to Roller release 6.1.6 or newer. If you cannot upgrade today, switch off the extension types in the web application descriptor or remove the XML-RPC servlet mapping, then restart.

## What the vulnerability is

Apache Roller is a multi-user blog server written in Java. Besides the web pages, it exposes an XML-RPC endpoint at the path `/roller-services/xmlrpc`, which blogging clients use to publish posts. The flaw sits in how that endpoint reads requests. According to the [NVD entry for CVE-2026-129448](https://nvd.nist.gov/vuln/detail/CVE-2026-129448), the endpoint takes vendor-defined extension types from the request and rebuilds objects from them before it has checked who is calling.

Deserialization of untrusted data (CWE-502) is a well-known class of bug. The server receives bytes from an outsider and rebuilds objects from them. If the attacker chooses which objects get built, the process can be pushed into running code of the attacker's choosing. Here the step happens before any login check, so the attacker needs no account, no password and no session. Network access to the endpoint is enough.

The record also explains why this identifier exists. The same underlying bug was first published under CVE-2026-82384, with a narrow scope: just Roller 6.1.5\. CVE-2026-129448 covers the same vulnerability across a much wider range: Apache Roller versions from 4.0.0 through 6.1.4 are listed as affected here. If a scanner or an advisory email shows you either identifier, treat them as one problem and use the same fix.

## Why it matters now

Three facts make this one urgent. First, the NVD description states that the issue is being actively exploited, and CISA lists it in the Known Exploited Vulnerabilities catalogue, which it reserves for flaws with evidence of exploitation in the wild. CISA lists use in ransomware campaigns as unknown, so do not read that as a promise that it is not happening.

Second, the attack is cheap. It needs no credentials, it works over the network, and the score reflects that: NVD records the attack vector as network, the complexity as low, privileges required as none and no user interaction. Anything that exposes a Roller XML-RPC endpoint to the internet, or even to a large internal network, is a target.

Third, the deadline is short. CISA's due date for federal agencies is November 23, 2026, one working weekend after the listing. You are probably not a federal agency, but the date is a fair signal of how fast CISA expects this to be handled. Blog servers are often forgotten machines: set up years ago, rarely patched, and not on anyone's asset list. That is exactly where an exploited flaw lingers.

For a similar case this week, see our post on [the exploited Apache Axis flaw](https://stackurity.ai/blog/apache-axis-cve-2026-90436-exploited-soap-fault-class-loading/), another Java service that parses attacker-controlled XML messages.

## Am I affected?

You are affected if you run Apache Roller from 4.0.0 up to 6.1.5 and the XML-RPC endpoint is reachable. Roller 6.1.6 and newer is the fixed line. The description names 6.1.5 as the version first published under the older identifier, so the safe reading is: anything below 6.1.6 needs the fix.

Disabling XML-RPC in the Roller administration screen does **not** protect you. The NVD description is explicit that older versions deserialize the request before they check that setting. The only protections are the upgrade or the two workarounds below.

To check one machine by hand, first find where Roller is deployed. These commands look for deployed web applications that contain Roller's descriptor and then show which servlet mapping and extension setting each one carries:

```
find / -name web.xml -path "*WEB-INF*" 2>/dev/null | xargs grep -il roller
grep -n -i "xmlrpc\|enabledForExtensions" /path/to/roller/WEB-INF/web.xml
ls /path/to/roller/WEB-INF/lib | grep -i roller
```

The last command lists the Roller libraries, whose file names carry the version. Replace `/path/to/roller` with the directory the first command found. Also check from the outside: ask your network team whether any firewall rule or reverse proxy forwards the path `/roller-services/xmlrpc` to the server.

One caveat applies to Linux distributions and vendors that package their own builds. If Roller reaches you inside a packaged product or a distribution package, the version number may not match the upstream one. Read the supplier's notice for CVE-2026-129448 before you decide a build is safe.

## How to fix CVE-2026-129448

1. List every Roller installation you own, including test blogs and old internal wikis built on it. Note the version, the host and whether the XML-RPC path is reachable from outside.
2. Move to Roller release 6.1.6 or newer. According to the NVD description, that release turns the extension types off, and it refuses XML-RPC calls whenever the feature is switched off. Back up the database and the deployed application first, and test a login and a post publish after the upgrade.
3. If you cannot upgrade today, apply a workaround and restart Roller: edit `WEB-INF/web.xml` so that `enabledForExtensions` is `false`, or delete the `/roller-services/xmlrpc` servlet mapping. Remember that the switch in the administration screen is not enough on older versions.
4. Block the path `/roller-services/xmlrpc` at your reverse proxy or firewall for as long as a vulnerable version runs, unless you need XML-RPC publishing from outside.
5. Because attackers have exploited the flaw, treat an exposed, unpatched Roller server as possibly compromised. Review web and application logs for unusual requests to the XML-RPC path, look for new files and processes, and rotate any credentials stored on that machine. CISA's own required action points to its forensics triage guidance for exploited flaws.

## How to check with Stackurity

Stackurity keeps one live inventory of the software on your servers, deployed applications, repositories and container images, and matches it against new vulnerability advisories and the CISA Known Exploited Vulnerabilities catalogue every hour. When a flaw like this one is added to the catalogue, that hourly match is what turns "CISA listed something" into a short list of your own assets, most urgent first.

Be clear about the limit. Stackurity reads installed packages, runtimes installed by hand and the libraries that deployed applications actually load. A blog application that someone unpacked by hand into a servlet container may not be listed as a product of its own, and libraries copied into an application outside a package manager are not covered. So for Roller specifically, use the hand check above to find installations first, and use Stackurity to cover the rest of the servers, images and repositories that carry known exploited flaws. After you fix something, Stackurity checks again and records whether the issue is really gone. The [remediation guide](https://stackurity.ai/docs/remediation) shows how the upgrade list is ordered and verified.

[Start a free Stackurity trial](https://app.stackurity.dev/signup?utm%5Fsource=blog&utm%5Fmedium=referral&utm%5Fcampaign=actively-exploited&utm%5Fcontent=apache-roller-cve-2026-129448-exploited-xmlrpc-deserialization)

## FAQ

### What is CVE-2026-129448?

It is a deserialization of untrusted data flaw in the XML-RPC endpoint of Apache Roller. An unauthenticated attacker can send a crafted request and run code on the server, because the endpoint deserializes extension types before it authenticates the caller.

### Which versions of Apache Roller are affected?

The NVD description lists Apache Roller versions from 4.0.0 through 6.1.4, and it says the same bug was first published as CVE-2026-82384 for version 6.1.5\. Move to 6.1.6 or newer.

### Is CVE-2026-129448 exploited in the wild?

Yes. The NVD description says the issue is being actively exploited, and CISA added it to the Known Exploited Vulnerabilities catalogue on November 20, 2026.

### Does turning off XML-RPC in the Roller admin screen protect me?

No. Older versions deserialize the request before they check that setting. Upgrade, or edit `WEB-INF/web.xml` so that `enabledForExtensions` is `false`, or delete the XML-RPC servlet mapping, and restart.

### What should I do if I cannot upgrade today?

Apply one of the two workarounds, restart Roller, block the XML-RPC path at your reverse proxy or firewall, and review your logs for unusual requests to that path.

### Can Stackurity find Apache Roller on my servers?

Stackurity matches the software it inventories against the CISA catalogue every hour, but a hand-deployed web application may not appear as a product of its own. Use the hand check to find Roller, and Stackurity to cover the rest of your estate.

Sources: [CISA Known Exploited Vulnerabilities catalogue](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search%5Fapi%5Ffulltext=CVE-2026-129448), [NIST National Vulnerability Database](https://nvd.nist.gov/vuln/detail/CVE-2026-129448), [Stackurity product facts](https://stackurity.ai/llms.txt).