Subscribe
0%
Illustration for: Apache Roller XML-RPC flaw CVE-2026-129448 exploited: older blogs are affected too — upgrade to 6.1.7

Apache Roller XML-RPC flaw CVE-2026-129448 exploited: older blogs are affected too — upgrade to 6.1.7

A new CVE published November 17 says Roller's unauthenticated XML-RPC deserialization bug reaches back to version 4.0.0 and is being actively exploited. Any self-hosted Roller blog older than 6.1.6 is exposed; here's how to patch, block the endpoint and check logs.

Listen to this article0:00 / 4:52

Apache published CVE-2026-129448 on November 17, warning that an unauthenticated remote-code-execution bug in the Apache Roller blog server affects versions 4.0.0 through 6.1.4 and is being actively exploited, Daily CyberSecurity reports, quoting the project's advisory. The flaw is rated CVSS 9.8.

Why it matters: the same bug was disclosed in September as CVE-2026-82384, but that record named only Roller 6.1.5 as affected. Admins running older releases may reasonably have concluded they were safe. The new CVE says they weren't — and attackers are already using it. No login is needed.

What the bug is

According to the CVE record, Roller's XML-RPC endpoint (/roller-services/xmlrpc) accepts "vendor extension types" and deserializes them before checking who sent the request (CWE-502). Because the servlet is mapped regardless of settings, turning XML-RPC off in the admin UI doesn't stop the parsing on vulnerable versions, the September record says. The fix disables those extension types and rejects XML-RPC requests when the feature is turned off.

Credit goes to researcher n0mi1k for the find and Matt Raible for reporting the wider version range, per the record.

Which versions are exposed

Roller version Status
4.0.0 – 6.1.4 Affected (CVE-2026-129448, Nov 17)
6.1.5 Affected (CVE-2026-82384, Sept 28)
6.1.6 Fixes the XML-RPC bug, but see below
6.1.7 Current release — recommended

The records disagree on the exact fix version: some fields list 6.1.5 as patched, while the descriptions say 6.1.6 or later. Given that 6.1.5 is itself named as affected in September's CVE, treat anything below 6.1.6 as vulnerable.

There's a second reason to skip straight to the newest build. On November 11 the Roller PMC announced 6.1.7, fixing 15 more CVEs that affect versions up to 6.1.6. They include a different deserialization bug in the XML-RPC client used for weblog update pings (CVE-2026-123374) — a malicious ping target can run code on your server — plus an XXE in AtomPub parsing and CSRF via GET on admin actions. Roller's downloads page lists 6.1.7 as the current release. The PMC warns some 6.1.7 changes affect existing sites, so read the release notes first.

How solid is the "exploited" claim?

It comes from Apache's own advisory, as quoted by Daily CyberSecurity and reflected in the CVE record. Apache hasn't said who is attacking, since when, or how many servers were hit. The CVE isn't in CISA's Known Exploited Vulnerabilities catalog yet, and OffSeq's tracker lists no public exploit module and no attack traffic on its sensors. We'd still act on the vendor's word.

What to do

  1. Upgrade to Roller 6.1.7. That covers this CVE, the September record and the November 11 batch.
  2. If you can't upgrade today, use the workaround from the advisory: set enabledForExtensions to false in WEB-INF/web.xml, or delete the /roller-services/xmlrpc servlet mapping. Then restart Roller — neither change takes effect until you do. Don't rely on the admin-panel XML-RPC switch.
  3. Block the endpoint at the edge. If nobody posts to your blog via XML-RPC clients, deny /roller-services/xmlrpc at your reverse proxy or WAF.
  4. Check for compromise. Look in access logs for POSTs to /roller-services/xmlrpc from unfamiliar IPs, especially since September. Then check the Roller host for new files in the web app directory, unexpected child processes of the Java servlet container and odd outbound connections. If anything looks wrong, rebuild rather than clean, and rotate database and admin credentials.
  5. Inventory forgotten blogs. Roller often runs old internal or project blogs that nobody updates — exactly the boxes the version-range correction is about.

Sources

  1. Daily CyberSecurity — CVE-2026-129448: Apache Roller RCE Actively Exploited, Patch Now securityonline.info
  2. ThreatInt — CVE-2026-129448 record cve.threatint.com
  3. oss-security (Openwall) — Apache Roller: 15 CVEs fixed in 6.1.7 openwall.com
  4. Daily CyberSecurity CVE Watchtower — CVE-2026-82384 securityonline.info
  5. OffSeq Threat Radar — CVE-2026-129448: Apache Roller deserialization radar.offseq.com
  6. Apache Roller website source — Downloads page apache.googlesource.com

#Apache#Apache Roller#CVE-2026-129448#CVE-2026-82384#RCE#deserialization#Java#patch now