Apache has warned that attackers are already exploiting a remote code execution flaw in Apache Roller, an open-source Java blogging platform. The bug, CVE-2026-129448, carries a CVSS score of 9.8. CISA added it to its Known Exploited Vulnerabilities catalog on November 20, and federal agencies have until Monday, November 23 to patch.
Roller runs on far fewer servers than the platforms that dominate the web. But the flaw requires no login and sits on a public-facing path, which is why any team running it should treat this weekend as a deadline of its own.
Which Apache Roller versions are affected by CVE-2026-129448
Apache announced the flaw on November 17. Rescana timestamps the announcement at 6:02 a.m. Eastern. The project's security notice did not hedge about the threat. The maintainers wrote, "This issue is being actively exploited," a line that The Hacker News also quoted on its vulnerability page.
The affected range is less settled. One source places the vulnerable range at Roller 4.0.0 through 6.1.4, while another places it at 4.0.0 through 6.1.5. Tuskira's advisory lists the fix as a later release, and Rescana names Apache Roller 6.1.6 as the fixed release, which it says shipped on September 24, 2026. Any installation older than 6.1.6 should be treated as vulnerable until someone confirms otherwise.
SecNews reports that the new flaw is tied to CVE-2026-82384, a predecessor patched in September 2026 that listed only Roller 6.1.5 as affected. According to that report, the November advisory widens the affected range beyond what the earlier fix covered. Administrators who upgraded to 6.1.5 in September may have assumed they were finished. They were not.
How the XML-RPC deserialization bug works
The vulnerability is an unauthenticated deserialization bug in Roller's XML-RPC endpoint. Deserialization flaws occur when an application rebuilds objects from data supplied by a user without checking what those objects are. When that check fails, an attacker can sometimes run code on the server. Because no login is required, anyone who can reach the endpoint over the network can attempt the attack.
Apache has not said how attackers are weaponizing the flaw or who is behind the activity. A Hacker News report that covers VMware, Cisco and Apache flaws together carries the headline "Hackers Exploit Critical VMware, Cisco, and Apache Flaws as Espionage Attacks Emerge," but the reporting available here does not tie this Roller flaw to a named group. Readers should not assume attribution until a credible investigator publishes evidence.
Exploitability is also disputed. A researcher blog argues that the 9.8 score reflects behavior at the parser stage and that real code execution depends on what sits on the server's classpath. That distinction matters for planning, since a high score does not mean every instance is equally compromised. It does not justify waiting, either. Rescana notes that its advisory review found no public proof-of-concept, and it is unknown whether mass scanning is underway.
Why the November 23 federal deadline matters
CISA added four flaws to KEV on November 20: VMware vCenter, Apache Roller, Cisco Expressway and SAP NetWeaver. Under BOD 26-04, federal agencies must patch all four by November 23. The Hacker News and Security Online both report the listing and deadline. KEV is CISA's catalog of vulnerabilities with evidence of real-world exploitation, and listed flaws carry hard dates for federal civilian agencies.
Federal civilian agencies running Roller or SAP NetWeaver must patch or confirm they are not affected by the deadline. Private organizations face the same exposure without the same clock, and the number of affected US Roller installations is unknown.
The SAP NetWeaver flaw, CVE-2025-42884, was added the same day. A researcher blog gives it a CVSS score of 6.5. USA 24 has covered the VMware vCenter zero-day and the Cisco Expressway flaw from the same batch, so defenders are looking at a cluster of enterprise infrastructure flaws being exploited in parallel.
Apache software is a recurring target in the catalog. SecNews cites CISA data showing 41 Apache product vulnerabilities added to KEV since November 2021. The same researcher blog also reports that CISA attached BOD 26-04 forensic triage requirements to three of the four entries, including Roller. If that is accurate, agencies will need to look for signs of compromise, not just install a patch.
What sources still disagree on
Two details need checking before anyone relies on them. The first is the KEV listing date. Rescana reports that a check on November 19 did not show the flaw in CISA's catalog, which conflicts with the November 20 addition reported elsewhere. Administrators should confirm the entry in CISA's live KEV catalog rather than rely on secondary reports.
The second is the last vulnerable release, where sources differ between 6.1.4 and 6.1.5. Because the sources that name a fix point to 6.1.6, the practical advice does not change. Upgrade to 6.1.6, and do not stop at 6.1.5 on the assumption that it is safe.
How to patch Apache Roller and check for compromise
Start with the version. Confirm the Roller release your server runs, and if it is anything older than 6.1.6, upgrade. Rescana and SecNews both point to 6.1.6 as the target. Download the release from Apache's official channels rather than a third-party mirror.
If you cannot patch by the deadline, Tuskira's guidance offers a stopgap: remove the /roller-services/xmlrpc servlet mapping and restart Roller. That closes the vulnerable path, but it can break any client that depends on XML-RPC publishing, so test the change before applying it to production.
Then check for evidence of compromise. Review web server and Roller logs for unusual XML-RPC requests, especially requests from unfamiliar addresses and any activity that predates your patch. Look for new or modified files, unexpected user accounts, and outbound connections from the Roller host. If the server was reachable from the internet while unpatched, a clean log review is necessary, but it does not prove the server was never touched.
If you are asking whether your Apache Roller server has already been hacked, the fastest answer comes from the logs. Start with the XML-RPC endpoint and work outward to the host.
What to watch next
Three developments matter most. First, whether CISA's live KEV entry is confirmed and the deadline holds. Second, whether Apache publishes a revised affected range that settles the 6.1.4 versus 6.1.5 question. Third, whether a public proof-of-concept appears, since that would make opportunistic exploitation far easier.
For federal teams, Monday is a checkpoint rather than the finish line. A patch installed without a log review may leave an earlier intrusion in place, and the forensic triage requirements reported for this batch make that review part of the job.




