CVE-2026-129448: Apache Roller XML-RPC RCE exploited in attacks, fixed in 6.1.6
Apache says unauthenticated attackers are already exploiting a critical deserialization flaw in Roller 4.0.0 through 6.1.4; here is how to patch or mitigate.
· 8 min read
Written by AI from the sources linked below. How we use AI
On this page
Apache has confirmed that attackers are already exploiting CVE-2026-129448, a critical flaw in Apache Roller, the open-source Java blogging server. The bug lets an unauthenticated attacker run code on the server through its XML-RPC endpoint, and Apache's advisory says plainly: "This issue is being actively exploited." The fix is Roller 6.1.6 or later. Switching XML-RPC off in the admin screen does not protect older installs, which makes this one easy to get wrong.
Key points
- CVE-2026-129448 is an unauthenticated deserialization flaw in the XML-RPC endpoint of Apache Roller 4.0.0 through 6.1.4, scored CVSS 3.1 9.8 (critical).
- Apache's announcement of 17 November 2026 says it is being actively exploited; Apache has not said who is behind the attacks or how many servers are affected.
- Upgrade to Apache Roller 6.1.6 or later. Without an upgrade, set
enabledForExtensionstofalseinWEB-INF/web.xml, or remove the/roller-services/xmlrpcservlet mapping, and restart. - Turning XML-RPC off in the administration UI is not enough on older versions, because they deserialize the request before checking that setting.
- It is the same bug as CVE-2026-82384, which Apache announced on 25 September 2026 but listed as affecting only Roller 6.1.5.
What to do
Who is affected. Anyone running Apache Roller 4.0.0 through 6.1.4 (affected per CVE-2026-129448). The earlier record, CVE-2026-82384, named 6.1.5 as affected. Apache's November text says the vulnerable behaviour is the same, so treat 6.1.5 as unsafe too and move to 6.1.6 or later, which is the version both advisories recommend.
Fix. Upgrade to Apache Roller 6.1.6 or later. Apache says this release disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.
Workaround if you cannot upgrade today. Apache gives two options, each followed by a restart of Roller:
- Set
enabledForExtensionstofalseinWEB-INF/web.xml. - Remove the
/roller-services/xmlrpcservlet mapping.
Do not rely on the checkbox in the admin UI. Apache says that disabling XML-RPC there "is not enough" for older versions.
How to check. Find the Roller version you deployed. If it is 6.1.5 or older, you are in scope. Apache has not published indicators of compromise, so we cannot give you a list of file names or addresses to hunt for. A reasonable first step, which is our suggestion and not Apache's, is to search your web server or reverse-proxy logs for requests to /roller-services/xmlrpc from addresses you do not recognise, and to treat a server that was reachable from the internet on an old version as possibly compromised.
What happened
On Tuesday 17 November 2026, the Apache Roller project posted a security announcement to the Apache announce list: "CVE-2026-129448: Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)". It rates the flaw Critical, CVSS 3.1 score 9.8, with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: reachable over the network, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability.
The description says the XML-RPC endpoint "accepts vendor extension types and deserializes them before authenticating the requester". The weakness class is CWE-502, deserialization of untrusted data. In practice an attacker sends a crafted serialized object to the endpoint, and the server processes it before checking who is asking. Deserializing attacker-controlled bytes in Java can lead to arbitrary code execution, and Apache lists remote code execution as the outcome.
The announcement credits "n0mi1k" as the finder and Matt Raible as the reporter. It links the fix, a GitHub pull request (apache/roller #171), and the earlier CVE.
BleepingComputer, which reported the advisory on 18 November, notes that Apache has not yet given details about the attacks, including who is responsible and how many servers have been compromised. We could find no other report that fills that gap.
Background
This is not the first time this bug has been announced. On 25 September 2026 the project published CVE-2026-82384, "Unauthenticated deserialization in the XML-RPC endpoint". That record listed only "Apache Roller 6.1.5" as affected, and its description added a detail that matters: the servlet "is mapped unconditionally, so parsing occurs even when the global XML-RPC feature is set to disabled". Apache said no non-default configuration was required.
The November announcement widens the picture. It says CVE-2026-129448 is "the same vulnerability as CVE-2026-82384" and that the vulnerable range actually runs from 4.0.0 through 6.1.4. In other words, the September record described the flaw but understated how far back it goes, and the November one corrects the version range and adds that the bug is being used in attacks. If you read only the September advisory, you could have concluded that 6.1.4 and earlier were fine. They are not.
Roller is a small project. BleepingComputer describes it as a Java-based group-blogging server "with a much smaller market share than modern content management systems and blogging platforms". That cuts two ways: fewer people run it, but the ones who do are often running old internal or hobby installs that nobody watches.
Roller has also had a heavy autumn of security fixes. Searching the Apache announce list for Roller turns up 18 advisories on 25 September, 15 on 11 November and this one on 17 November.
The numbers
The Roller advisories on the Apache announce list this autumn, counted by day of announcement:
| advisories | |
|---|---|
| 25 Sep | 18 |
| 11 Nov | 15 |
| 17 Nov | 1 |
Source: Apache announce list (lists.apache.org), search for Roller
The November batch of 15 covers a wide mix of problems: stored and reflected cross-site scripting, XML external entity processing in AtomPub parsing, cross-site request forgery in administrative actions, exposure of other users' email addresses through search, a weblog template that exposes another user's password hash, and a separate deserialization bug, CVE-2026-123374, in weblog update ping responses. The September batch includes server-side request forgery, XXE in trackback and OPML parsing, an OAuth endpoint that trusts a request-supplied identity, and a template include that escapes the Velocity sandbox.
We list these to show the scale of the clean-up, not to say each one is being attacked. Of everything on the list, only CVE-2026-129448 carries the "actively exploited" statement from Apache.
The score itself is as bad as the scale goes: 9.8 out of 10 under CVSS 3.1. Our own explainer on what a CVSS score means covers how that vector string turns into a number.
How it works
Java's built-in serialization turns an object into bytes and back. The danger is in the "back": when a program rebuilds objects from bytes an attacker supplied, the attacker influences which classes get instantiated and which code runs while they are rebuilt. If suitable classes exist on the server's classpath, a crafted payload can chain them into command execution. This family of bugs has produced critical Java vulnerabilities for years, and defenders usually fix it by refusing to deserialize arbitrary types or by filtering what is allowed.
The XML-RPC protocol carries typed values in XML. Roller's endpoint accepted "vendor extension types" in that XML and turned them into objects while parsing the request. Because the parsing happened before authentication, the attacker did not need an account. The code that decides whether XML-RPC is switched on ran after the damage was possible, which is why the admin-UI toggle does not help on old releases.
Apache's fix in 6.1.6 takes both steps at once: it disables the extension types, and it rejects XML-RPC requests when the feature is turned off. The two workarounds Apache offers for people who cannot upgrade each cut the path in a different way. Setting enabledForExtensions to false stops the dangerous types from being processed, and removing the servlet mapping removes the endpoint from the web application entirely.
What it means
For administrators. If you run Roller on the internet, this is a same-day job. Apache says the flaw is being exploited, the attack needs no credentials, and the vulnerable path is reachable by default. Patch, then check logs, then consider whether the server holds anything an attacker could reuse: database credentials in configuration files, API keys, or access to internal networks. Code execution runs with the privileges of the application process, so what that process can reach matters.
For people who read only one advisory. The September announcement understated the affected versions. Anyone who saw only that notice and decided their 6.1.4 install was not affected should look again. This is a reminder to re-check advisories when a later record says "same vulnerability".
For the wider ecosystem. Small, long-lived open-source servers are a recurring target, because their users patch slowly and their maintainers are few. BleepingComputer also points to other Apache products in the news this year: it recalls that CISA flagged a 13-year-old Apache ActiveMQ vulnerability (CVE-2026-34197) as exploited in April, and that Apache fixed a critical HTTP/2 module flaw in Apache HTTP Server earlier this month. Those are different products with different bugs, and we make no claim that the attacks are connected.
What we don't know yet
- Who is exploiting it and how widely. Apache gave no details, and BleepingComputer says the same.
- Whether exploitation began before the September advisory. Apache's text only says the issue "is being actively exploited". We have no date.
- Indicators of compromise. None have been published by Apache that we could find.
- CISA status. At the time of writing we could not confirm a listing in CISA's Known Exploited Vulnerabilities catalog. Some trackers show no such entry, and the OpenCVE record labels exploitation as "none", which conflicts with Apache's own statement. We rely on Apache's statement.
- Public exploit code. Trackers disagree on whether proof-of-concept code is public. One says none is indexed, another lists one. We could not verify either, so plan as though working exploit code exists.
What to watch next
- A CISA KEV entry, which would set a federal patching deadline and signal wider exploitation.
- Further detail from the Roller project on when attacks began and how to tell whether a server was hit.
- Whether the project publishes more fixes, given the volume of reports this autumn.
- Any follow-up from the researchers credited with finding and reporting the bug.
We will add a dated update to this article if Apache or CISA publishes more.
Sources
- Apache announce list: CVE-2026-129448, Unauthenticated deserialization in the XML-RPC endpoint (17 November 2026) (primary source)
- Apache announce list: CVE-2026-82384, the original announcement (25 September 2026)
- BleepingComputer: Apache warns of Roller RCE vulnerability exploited in attacks
- OpenCVE record for CVE-2026-129448
- Apache Roller fix: apache/roller pull request 171
Written by
The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.
Read next
Java4Shell CVE-2026-114938: OpenJDK Base64 RCE on AVX-512 CPUs, what to patch
A heap overflow in HotSpot's AVX-512 Base64 decoder affects OpenJDK 17.0.6 and later on x86-64; here is who is exposed, how to check and the flag that turns off the bad code.
audiotale.net team8 min read
CVE-2026-119618: Apache httpd 2.4.71 fixes critical mod_http2 RCE flaw
Apache HTTP Server 2.4.55 to 2.4.70 are affected by a critical mod_http2 race condition that can lead to remote code execution; 2.4.71, released 11 November 2026, fixes it.
audiotale.net team6 min read
OpenJDK October 2026 advisory: 47 Java CVEs and 6 JavaFX, Corretto 25.0.5
The 20 October 2026 OpenJDK advisory fixes 47 OpenJDK and 6 OpenJFX CVEs, none above CVSS 7.5; here is who is affected and how to update.
audiotale.net team6 min read