# Apache Roller RCE CVE-2026-129448 (CVSS 9.8): One Unauthenticated XML-RPC Request Runs Code on Your Blog Server — Actively Exploited, Patch to 6.1.6
If you run Apache Roller — the ASF’s Java-based multi-user blog platform — stop reading and check your version right now. Apache confirmed on November 17, 2026 that a critical remote code execution flaw in Roller’s XML-RPC endpoint is being actively exploited in the wild. Tracked as **CVE-2026-129448** and rated **CVSS 9.8 (Critical)**, it lets a remote attacker with no credentials run arbitrary code on your server with a single crafted request.
## What the vulnerability is
CVE-2026-129448 is a deserialization-of-untrusted-data bug (CWE-502) in Roller’s XML-RPC service. The endpoint at `/roller-services/xmlrpc` accepts vendor extension types and deserializes them into Java objects before it ever checks who is asking. That ordering is the whole problem: the request is parsed and deserialized *before authentication*, so an attacker who can reach the endpoint needs no account at all.
An attacker sends a crafted XML-RPC request containing a malicious serialized vendor-extension object. Roller deserializes it — and the attacker gets remote code execution on the server. No login, no user interaction, no multi-step chaining. Because the endpoint runs inside the Java web application’s process, the shell lands with whatever privileges Roller is running with.
## Affected versions
This hits **Apache Roller 4.0.0 through 6.1.4**. The nasty part: this is not a brand-new bug. It’s the same underlying vulnerability as **CVE-2026-82384**, which Roller patched back in September 2026 — but that fix only covered version 6.1.5. The September patch was incomplete, leaving the entire 4.0.0–6.1.4 range exposed, and attackers are now exploiting exactly that gap.
## Why it matters
CVSS 9.8 with the vector `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` is about as bad as network-facing bugs get: remotely exploitable, low complexity, no privileges, no interaction, and the impact hits confidentiality, integrity, and availability all at once. For a blog platform this is corporate and government blog deployments with legacy, internet-exposed instances — precisely the kind of server that gets bolted on and forgotten. Once an attacker has RCE on the blog box, it’s a springboard into the rest of the network.
## What to do
**Patch:** Upgrade to **Apache Roller 6.1.6 or later**. The 6.1.6 release disables the vulnerable extension types and rejects XML-RPC requests when the feature is disabled. 6.1.7 is the current best-available release.
**Can’t patch immediately?** Two web.xml-level mitigations work, then restart Roller:
– Set `enabledForExtensions` to `false` in `WEB-INF/web.xml`, or
– Remove the `/roller-services/xmlrpc` servlet mapping.
**Critical gotcha:** disabling XML-RPC through the Roller administration UI is **not** enough. Older versions deserialize the request before they check that admin setting, so the vulnerable code path still runs. The mitigation has to happen at the web.xml or servlet-mapping level, and you must restart for it to take effect.
## Action items
1. Inventory every Apache Roller instance you run — including forgotten legacy deployments.
2. Check whether any are internet-exposed; those are your immediate risk.
3. Patch to 6.1.6/6.1.7, or apply the web.xml mitigation and restart immediately.
4. If you’ve been exposed, treat the server as compromised and hunt for web shells and access to the broader network compartment.
This one is confirmed exploited right now, so don’t wait for a scheduled maintenance window. Patch today.