Apache Roller Vulnerability CVE-2026-129448: Exploited XML-RPC Flaw Lets Attackers Run Code With No Login, and the Version to Install
Apache says CVE-2026-129448 in Apache Roller is being actively exploited. Versions 4.0.0 through 6.1.4 let an attacker with no login run code through XML-RPC. Upgrade to 6.1.6 or later. Turning off XML-RPC in the admin screen does not fix it.
Where Worldwide
On this page 9 sections
Apache Roller, Apache's blog server software, has a critical flaw that lets an attacker with no account run their own code on the server, and Apache says attackers are already using it. If your organization runs Roller versions 4.0.0 through 6.1.4 for a company blog, an intranet news page or a customer-facing site, upgrade to 6.1.6 or later this week.
The flaw is tracked as CVE-2026-129448. It was announced on the oss-security mailing list on Tuesday, 17 November 2026, with the label "Severity: Critical". Apache's Roller security page says plainly: "This issue is being actively exploited."
What happened with CVE-2026-129448
Roller has an XML-RPC endpoint, which is an interface that lets other programs talk to the server. According to Apache, that endpoint "accepts vendor extension types and deserializes them before authenticating the requester".
Here is what that means. Deserialization is when a server takes data someone sent it and turns it back into working objects in memory. If the data comes from a stranger, a carefully crafted message can trick the server into running code. The real problem is the order: Roller does this before it checks who is asking. So an attacker needs no password, no account and no prior access.
Apache sums up the result: the flaw "allows an unauthenticated remote attacker to execute arbitrary code". In plain terms, anyone who can reach the endpoint over the network can make the server run their commands.
Apache Roller exploit: what is confirmed and what is not
| Claim | Status | Where it comes from |
|---|---|---|
| Severity is Critical | Confirmed | oss-security announcement |
| Versions 4.0.0 through 6.1.4 are affected | Confirmed | Apache Roller security page |
| Attackers need no login | Confirmed | Apache Roller security page |
| The flaw is being actively exploited | Confirmed by Apache | Apache Roller security page |
| Recommended fix is 6.1.6 or later | Confirmed | Apache Roller security page |
| Disabling XML-RPC in the admin UI is a workaround | No: Apache says it is not enough | Apache Roller security page |
| Same vulnerability as CVE-2026-82384 | Stated by Apache, not explained | Apache Roller security page |
| Who is attacking, and how many sites are hit | Not known | Not in the sources we checked |
| A numeric severity score | Not confirmed | Not in the sources we checked |
| Signs of compromise to look for | Not published | Not in the sources we checked |
If you see a specific score or attack numbers elsewhere, treat them as unconfirmed until Apache or the announcement says the same.
Which Apache Roller versions are affected, and is 6.1.5 enough?
Apache's page describes the affected range as "Apache Roller from 4.0.0 before 6.1.5" and also as versions 4.0.0 through 6.1.4. Read alone, that makes 6.1.5 look like the first safe release.
The same page, though, says: "Users are recommended to upgrade to Apache Roller 6.1.6 or later". The sources we checked do not explain why the advice skips 6.1.5. When the vendor's stated fix and its affected range don't quite line up, follow the stated fix. Install 6.1.6 or later, and if a server is already on 6.1.5, plan to move it up too. We covered why a version number on its own doesn't prove you're protected in Updated Is Not the Same as Patched.
Can you just disable XML-RPC in Apache Roller?
No. Apache says directly: "Disabling XML-RPC in the administration UI is not enough."
The sources don't explain why the admin setting falls short, so don't rely on it as protection. A settings toggle is not a patch. Upgrading is the fix Apache gives.
How CVE-2026-82384 fits in
Apache describes CVE-2026-129448 as "the same vulnerability as CVE-2026-82384". The sources we checked don't say why there are two identifiers. In practice: if your team has a ticket or scanner finding for CVE-2026-82384, link it to this one. If you thought you dealt with CVE-2026-82384 earlier, check that the server is on 6.1.6 or later now. Don't assume the earlier work covered it.
What to do this week
| Step | What to do | How to check it is done |
|---|---|---|
| 1. Find every install | List every Roller server: public blogs, intranet sites, staging copies and old instances nobody has touched in years | You have a written list with an owner for each one |
| 2. Check the version | Anything from 4.0.0 through 6.1.4 is affected | Compare the version each install reports, or your deployment records, against that range |
| 3. Upgrade | Move every affected server to Apache Roller 6.1.6 or later | Each server reports 6.1.6 or later after the upgrade |
| 4. Don't count on the toggle | Turning off XML-RPC in the administration UI does not fix it | The upgrade is done, whatever the XML-RPC setting says |
| 5. If you cannot upgrade today | Take the affected site offline or off the public internet until you can | The server cannot be reached from outside |
| 6. Check for compromise | The flaw is being exploited and needs no login, so treat any affected server that was reachable as possibly compromised | Look for unfamiliar files, new accounts and unexpected processes, and change passwords and keys stored on the server, such as database credentials |
Apache has not published signs of compromise in the sources we reviewed. If you find something you can't explain, get help investigating before you trust the server again.
Why this matters for a business website
Blog servers tend to get set up for a launch or a marketing push and then left alone. They keep running long after the person who installed them has moved on. That's exactly the kind of system this flaw punishes. No login is needed, so it doesn't matter how strong your Roller admin passwords are.
Running code on a server means the attacker acts with the server's own permissions. Depending on how it was set up, that could mean changing your public pages, planting malicious content for visitors, reading the database behind the site, or using the server to reach other systems on the same network. An intranet blog that's only reachable inside the office is less exposed than a public one. But it's still a foothold if any other device on that network is already compromised.
If nobody at your company can say right now which version your blog runs, that's the first problem to fix. We wrote about it in Who Is Patching the Software That Runs Your Business?. If you host your own servers, our self-hosting and infrastructure page explains how we set them up to be kept current.
Apache Roller vulnerability questions people are asking
Is CVE-2026-129448 being exploited?
Yes. Apache's Roller security page says: "This issue is being actively exploited." The sources don't say who is behind the attacks or how many servers have been hit.
Which versions of Apache Roller are affected?
Versions 4.0.0 through 6.1.4, according to Apache.
What version of Apache Roller fixes CVE-2026-129448?
Apache recommends upgrading to Apache Roller 6.1.6 or later. The affected range ends at 6.1.4, but the stated recommendation is 6.1.6, so install that.
Does an attacker need a login?
No. Apache says the flaw lets an unauthenticated remote attacker run arbitrary code, because the XML-RPC endpoint processes the data before checking who sent it.
Can I disable XML-RPC instead of upgrading?
No. Apache says disabling XML-RPC in the administration UI is not enough.
What is the CVSS score for CVE-2026-129448?
The oss-security announcement rates it Critical. We did not find a numeric score in the primary sources we checked.
Is CVE-2026-82384 the same flaw?
Apache describes CVE-2026-129448 as the same vulnerability as CVE-2026-82384. The sources don't explain why it has two identifiers.
Is this an XML-RPC deserialization vulnerability?
Yes. Apache says the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. That's the root cause.
The bigger lesson
Two things in this advisory apply well beyond Roller. First, software has to check who is asking before it does anything with what they sent. Doing it the other way round is what turned an interface into a way to run code. Second, a switch in an admin screen is not the same as a fix. Apache says so directly here. The protection is the upgrade, confirmed on every server you own, including the ones nobody remembers.
See how we lock down servers and websites at /tech/security-hardening, or ask us to check yours at /get-a-quote/tech.
Get security alerts like this by email, plus our free checklist, at /security-alerts.
Sources: Apache Roller security advisories; oss-security announcement of CVE-2026-129448.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Linux KVM Vulnerability CVE-2026-99312: AMD Hosts With Nested Virtualization Affected, What Is Confirmed and How to Check Yours
A Linux kernel flaw in the KVM hypervisor, CVE-2026-99312, affects hosts with AMD processors and nested virtua...
PHP Critical Vulnerability: Seven RCE Flaws Fixed in PHP 8.5.13 and 8.6.0, Which Version to Install for Your Branch and Who Is Exposed
PHP's 19 November 2026 security releases fix seven critical remote code execution flaws. Here is which version...
PHP Session Vulnerability: CVE-2026-126714 and CVE-2026-115560 Can Lead to Remote Code Execution, Fixed in PHP 8.5.13, and What to Check This Week
PHP has fixed two session flaws, CVE-2026-126714 and CVE-2026-115560, that can lead to remote code execution....