Apache Roller CVE-2026-129448 Is Exploited: Affected Versions, Upgrade to 6.1.7 and an Interim Workaround

Published:

CISA added Apache Roller flaw CVE-2026-129448 to its Known Exploited Vulnerabilities (KEV) catalog on November 20, 2026, with a federal deadline of November 23. It is an unauthenticated remote code execution bug in Roller’s XML-RPC endpoint, scored 9.8 out of 10. The fix has been available since September, so the risk falls on anyone still running an old Roller blog server. Here are the affected versions, the releases to move to, an interim workaround and what is still unconfirmed.

What is CVE-2026-129448?

Apache Roller is an open-source, Java-based blog server. Per Security Affairs’ summary of the CISA batch, CVE-2026-129448 is a deserialisation-of-untrusted-data flaw in the XML-RPC endpoint that affects Roller 4.0.0 through 6.1.4 and lets an unauthenticated remote attacker run code, and the maintainers confirmed exploitation in the wild. Phoenix Security’s write-up adds the mechanism: Roller sets the enabledForExtensions option of its XML-RPC library to true in WEB-INF/web.xml, which allows a vendor data type that carries serialised Java objects, and the request is parsed before any login check. It also says the endpoint is reachable at /roller-services/xmlrpc (or /roller/roller-services/xmlrpc when Roller is not the root application) whether or not an admin has turned XML-RPC on.

Which versions are affected, and which are fixed?

  • CVE-2026-129448: Roller 4.0.0 through 6.1.4.
  • CVE-2026-82384: the same bug, which Roller’s security page lists as “Critical” and fixed in 6.1.6. It names version 6.1.5 as affected. Together, that makes 4.0.0 through 6.1.5 the range to treat as vulnerable.
  • Fixed: Roller 6.1.6, released September 24, 2026, is the first fixed release. Roller 6.1.7, released November 11, is the current one and fixes more problems, including another deserialisation flaw, CVE-2026-123374, in weblog update ping responses.

Some aggregator pages list 6.1.5 as the fixed version. That is wrong: 6.1.5 is the version the older CVE names as affected, so go to 6.1.6 at the least and preferably 6.1.7. Roller’s security page says older releases are not patched in place, so the remedy is to upgrade.

What is the timeline?

  • Late September 2026: Roller 6.1.6 ships with a large batch of fixes, and CVE-2026-82384 is published for 6.1.5. Phoenix Security says public proof-of-concept tooling appeared around then.
  • November 11: Roller 6.1.7 is released.
  • November 17: CVE-2026-129448 is published, with Apache saying it is being exploited and widening the range to 4.0.0 through 6.1.4.
  • November 20: CISA adds it to KEV, along with Cisco Expressway, VMware vCenter and SAP NetWeaver, due November 23.

What if you cannot upgrade yet?

These interim steps come from Phoenix Security, not from Apache’s page, and Phoenix sells security products, so treat them as a stop-gap:

  1. Set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller.
  2. Block POST /roller-services/xmlrpc at your reverse proxy or web application firewall. If a desktop blogging client needs XML-RPC, allow only its source addresses.
  3. Do not rely on switching XML-RPC off in the admin screen. According to Phoenix, that setting is read after the vulnerable parsing step.

Whichever route you take, check your web server logs for unexpected requests to the XML-RPC path, and look for unfamiliar files or processes if the server was reachable from the internet. Phoenix notes that public detection rules matching only the path may fire on normal blogging-client traffic.

How worried should you be?

Take it seriously if you run an old, internet-facing Roller. Two cautions apply. First, Phoenix Security points out that the exploitation claim traces back to Apache’s own notice and says no other source had independently confirmed it as of November 19; CISA’s KEV listing, on November 20, now states evidence of active exploitation too. Second, whether code actually runs depends on the Java version and libraries on the server. Phoenix cites one lab analysis in which a stock modern install blocked the default exploit chains, with older 4.x and 5.x builds on older Java described as the softest targets. The unsafe parsing itself happens on every affected version regardless.

What is still unknown?

  • Who is exploiting it, and how many servers have been hit. No source we read names an attacker or gives a victim count.
  • How many Roller servers are exposed to the internet. No public scan count exists.
  • Whether Apache will add CVE-2026-129448 to its security page. It was not listed there when we checked.

For the rest of the batch, see our posts on the Cisco Expressway flaw and the VMware vCenter zero-day, and last week’s Exploited This Week round-up.

Sources

Image: Apache Roller logo, Apache Software Foundation, via Wikimedia Commons.

Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.

Saif Ali Tai
Saif Ali Taihttps://xplorely.com/
I'm Saif Ali Tai, a tech blogger and software engineer with 8+ years of experience building apps, and I run StepPhase as its editor. I cover technology news, AI tools and security stories that matter to everyday users. Articles here are drafted with AI assistance and checked against the sources linked in each post.

Related articles

Recent articles