top of page

Apache Roller CVE-2026-129448: Same XML-RPC Bug Apache Fixed in September, but the First Advisory Named Only One Version. Roller 4.0.0 Through 6.1.4 Were Exposed All Along, and It Is Being Exploited

Writer: Patrick Duggan
Patrick Duggan
36 minutes ago
3 min read

If you run Apache Roller, the blog server, upgrade to 6.1.7 today. If you can't, cut off the XML-RPC endpoint at the servlet level, not in the admin screen. Apache said on November 17 that an unauthenticated remote code execution bug in Roller's XML-RPC endpoint "is being actively exploited."


The catch is in the version numbers. This is not a new bug.



What Apache said in September, and what it says now


In September, Apache fixed CVE-2026-82384, "Unauthenticated deserialization in the XML-RPC endpoint," rated Critical and fixed in Roller 6.1.6. That advisory listed only Roller 6.1.5 as affected.


On November 17, Apache's Roller project published CVE-2026-129448. Its description says it "is the same vulnerability as CVE-2026-82384," and that it affects every version from 4.0.0 through 6.1.4. CVSS 3.1 is 9.8. No login is needed.


So for about two months, an administrator on Roller 5.x or 6.0 who read the September advisory had good reason to think the bug didn't apply to them. It did. The fix was always the same: move to 6.1.6 or later. The second CVE corrects the version range.



What the bug is


Roller's XML-RPC endpoint accepts "vendor extension types" and deserializes them before it checks who is asking. A crafted request to that endpoint runs code on the server, with no account needed.


Apache's advisory makes a point that matters for anyone who thinks they already turned XML-RPC off: "Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting." The switch in the admin screen is checked after the damage is done.



What to do


  1. Upgrade to Roller 6.1.7. Apache's advisory says 6.1.6 or later fixes this bug. We say 6.1.7, released November 11, because Roller's security page lists 14 more fixes in it, including CVE-2026-123374, a separate deserialization flaw in weblog update ping responses.

  2. If you can't upgrade today: set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller. Those are Apache's two stated workarounds.

  3. Block the path at the edge too. If nothing you run posts to /roller-services/xmlrpc (most blogs stopped using desktop blog editors years ago), a reverse proxy or WAF rule that refuses it costs nothing.

  4. Assume compromise if it was exposed. Apache says the bug is being exploited and hasn't published indicators, so you can't check against a list. Look for unexpected processes running as the Roller or servlet-container user, new files in the webapp directory, and outbound connections from the server that you can't explain.


What is not known


Apache hasn't said who is exploiting this, how many servers are affected, or since when. No indicators of compromise were published in the advisory or in BleepingComputer's report, so we have added nothing to our feed for it. CISA had not added CVE-2026-129448 to its Known Exploited Vulnerabilities catalog when we checked the catalog JSON this morning. VulnCheck lists it as exploited.



What our edge saw


We checked our own sensors for the Roller path since October 19: about 467,000 edge blocks, 75,000 decoy hits and 627 requests that reached the origin. Zero requests for /roller-services. We did see 735 decoy hits on "xmlrpc.php," but that is WordPress, a different product, and not evidence of Roller scanning. We don't run Roller, so a scanner that fingerprints first would skip us. Zero here tells you little about the internet.



How we know


We read the advisory itself on the Apache mailing list archive (posted by Arnout Engelen to the Roller user list, November 17), and Roller's security page, which lists CVE-2026-82384 as fixed in 6.1.6 and the 6.1.7 release of November 11. Credit in the advisory: n0mi1k (finder) and Matt Raible (reporter).



Sources


  • Apache Roller, "CVE-2026-129448: Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)," lists.apache.org/thread/lnz4s26tv6hdo03wngtdbpfj4hg4gtds, November 17, 2026.

  • Apache Roller security page, roller.apache.org/security.html (CVE-2026-82384, fixed in 6.1.6; the 6.1.7 release notes).

  • BleepingComputer, "Apache warns of Roller RCE vulnerability exploited in attacks," November 18, 2026.

  • CISA Known Exploited Vulnerabilities catalog JSON, read November 18, 2026.

  • VulnCheck KEV.



Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page