Apache Roller Vulnerability CVE-2026-129448: Exploited No-Login Code Execution Flaw, Why Disabling XML-RPC Is Not Enough, and the Version to Install
Apache confirms CVE-2026-129448 in Apache Roller is being actively exploited. An attacker with no login can run code on the server. Here is what is confirmed, what is not known, and why to upgrade to 6.1.6 or later this week.
Where Worldwide
On this page 9 sections
Apache has confirmed that a critical flaw in Apache Roller, tracked as CVE-2026-129448, lets an attacker with no login run their own code on the server. It also says the flaw is being actively exploited. If your company runs any Roller version from 4.0.0 up to 6.1.4, upgrade to Roller 6.1.6 or later this week. Switching off XML-RPC in the admin screen does not protect you.
What is CVE-2026-129448?
CVE-2026-129448 is a remote code execution (RCE) vulnerability in Apache Roller. The public disclosure on the oss-security mailing list, posted on Tuesday, 17 November 2026, sums it up in one sentence: "Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code."
In plain English: someone on the internet with no username or password can make your Roller server run commands they choose. Code running on your server can usually read anything the server can read and change anything it can change. It can also be used as a foothold to reach other systems the server can reach.
The same disclosure rates it CVSS 3.1: 9.8, critical. The parts of the score show why it rates so high:
| Part of the score | What it means |
|---|---|
| AV:N | The attack comes over the network |
| AC:L | Low complexity, no special conditions needed |
| PR:N | No account or privileges needed |
| UI:N | Nobody on your side has to click anything |
| C:H, I:H, A:H | High impact on data secrecy, data integrity and uptime |
Which Apache Roller versions are affected?
Apache's security page for Roller gives the affected range as "Apache Roller from 4.0.0 before 6.1.5". The oss-security post gives the same range as 4.0.0 through 6.1.4.
One detail needs attention. Apache's advice reads: "Users are recommended to upgrade to Apache Roller 6.1.6 or later." The sources we checked do not say why the advice names 6.1.6 and not 6.1.5. Until that is cleared up, aim for 6.1.6 and do not stop at 6.1.5.
Is the Apache Roller vulnerability being exploited?
Yes, according to Apache. Its Roller security page states: "This issue is being actively exploited."
The sources we checked do not say who is exploiting it, how many servers have been hit or what attackers do once they get in. They also give no indicators of compromise, such as file names, addresses or log entries to search for. We will not guess at any of these. If you ran an affected version that could be reached from the internet, assume someone may have tried it.
What is confirmed and what is not known
| Question | Status |
|---|---|
| CVE ID | Confirmed: CVE-2026-129448 |
| Login needed to attack? | Confirmed: no, unauthenticated |
| Severity | Confirmed: CVSS 3.1 score of 9.8, critical |
| Affected versions | Confirmed: 4.0.0 before 6.1.5 |
| Version Apache recommends | Confirmed: 6.1.6 or later |
| Exploited in the wild | Confirmed by Apache |
| Does turning off XML-RPC in the admin UI help? | Confirmed: not enough on its own |
| Why the advice names 6.1.6, not 6.1.5 | Not explained in the sources |
| Who is behind the attacks | Not known |
| Number of servers hit | Not known |
| Signs of compromise to look for | Not published in the sources |
How to fix the Apache Roller vulnerability this week
| Step | What to do | How to check |
|---|---|---|
| 1. Find every install | List every server running Roller, including staging, test, old campaign blogs and anything a past contractor set up | Ask your hosting provider and developers, and check your server inventory |
| 2. Check the version | Anything from 4.0.0 up to and including 6.1.4 is affected | Write down the version number for each install |
| 3. Upgrade | Move to Apache Roller 6.1.6 or later, and take a backup first | Confirm the version shows 6.1.6 or later after the upgrade |
| 4. On 6.1.5? | Move to 6.1.6 anyway, because that is the version Apache recommends | Same check as step 3 |
| 5. Do not rely on XML-RPC settings | Turning off XML-RPC in the admin UI is not a fix | Treat the upgrade as the only fix |
| 6. Review exposed servers | If an affected version was reachable from the internet, have someone review the server and change any passwords or keys stored on it | Record who checked it and when |
If you cannot upgrade today, the upgrade is still the only fix the sources name. Cutting off public access to the server until you can patch limits who can reach it in the meantime.
Why turning off XML-RPC is not enough
The oss-security disclosure warns: "Disabling XML-RPC in the administration UI is not enough." This matters because many admins switch off a feature in the settings screen and assume they are covered. The disclosure does not explain in detail why the setting falls short. What it makes clear is that the setting is not a substitute for upgrading. Do not mark the server as handled until it runs 6.1.6 or later.
Why this matters for a business website
A blog server is easy to forget. It often goes live for a launch or a content push, then sits for years with nobody owning updates. With this flaw, any Roller server still on an affected version is open to attackers who need no login and no click from anyone.
The risk does not stop at the blog. If the Roller server shares a host, a database, or credentials with your main website, customer systems, or internal network, an attacker who can run code on it may be able to go further. A defaced blog is a bad day. A server used as a way into everything else is much worse.
If nobody at your company can say who patches the Roller server, that is the first gap to close.
Apache Roller vulnerability questions people are asking
What is CVE-2026-129448?
It is a critical flaw in Apache Roller that lets an unauthenticated remote attacker execute arbitrary code on the server. It is rated CVSS 3.1: 9.8.
Is Apache Roller 6.1.4 vulnerable?
Yes. Both sources include 6.1.4 in the affected range, which starts at 4.0.0.
What version fixes the Apache Roller vulnerability?
Apache recommends upgrading to Apache Roller 6.1.6 or later.
Is Apache Roller 6.1.5 safe?
Apache's affected range stops before 6.1.5, but its upgrade advice names 6.1.6. The sources do not explain the gap, so upgrade to 6.1.6.
Is disabling XML-RPC enough to stop the Apache Roller exploit?
No. The disclosure says disabling XML-RPC in the administration UI is not enough.
Is the Apache Roller RCE being exploited?
Yes. Apache states the issue is being actively exploited. Who is behind it and how many servers have been hit are not known.
Do attackers need a password?
No. The flaw requires no authentication and no user interaction.
How do I know if my Roller server was hacked?
The sources do not publish signs of compromise. If an affected version was exposed to the internet, have the server reviewed and change any passwords or keys stored on it.
The bigger lesson
Software that nobody remembers is software that nobody patches. When a flaw like this lands with active exploitation, the businesses that come through fine already know what they run, which version it is and who updates it. Keep that list, give every server an owner, and treat settings-screen workarounds as stopgaps, never fixes.
Want your servers and sites hardened and kept patched? See security hardening or get a quote.
Get security alerts like this by email, with our free checklist, at security alerts.
Sources: Apache Roller security page; oss-security disclosure, 17 November 2026.
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
AI Agent Attack on Epoch AI: Test Agents Tried SQL Injection on a Live Website, Trajectory Labs Pauses Testing, and What Businesses Should Check
AI agents in alignment tests run by Trajectory Labs tried to hack Epoch AI's live website, including a SQL inj...
Puppet Enterprise Vulnerability CVE-2026-115731: CISA Lists the Exploited Flaw, the Certificate Key Risk, and the Fixed Versions to Install
CISA added Puppet Enterprise flaw CVE-2026-115731 (CVSS 9.4) to its exploited list on November 17. Here is wha...
Agent Framework PyPI Malware
Attackers published malicious releases of Microsoft's official Agent Framework package on PyPI on November 17,...