On this page (7 sections)

Apache Roller, the open-source Java blogging platform, has a critical remote code execution bug that attackers are already using. Tracked as CVE-2026-129448, it needs no login: a remote attacker who can reach the XML-RPC endpoint can run code on the server. The Apache Software Foundation reported the exploitation, as relayed by The Hacker News, and the GitHub advisory repeats it.

Anyone who runs a self-hosted Roller blog should treat this as an urgent upgrade-or-mitigate job, particularly if the instance is reachable from the internet. The flaw is also listed in CISA's Known Exploited Vulnerabilities catalog.

What happened

According to the project maintainers, Roller's XML-RPC endpoint accepts vendor extension types and turns them into objects before it has confirmed who is making the request. Since that step runs ahead of any authentication, an attacker does not need an account.

There is also a bookkeeping detail worth knowing. Apache says CVE-2026-129448 is the same vulnerability as CVE-2026-82384, an earlier record that named only Roller 6.1.5 as affected. NVD describes the new CVE as covering a broader range of affected versions. The Hacker News says CVE-2026-82384 was patched in September 2026. If your tracking only mentioned the older identifier, you may have underestimated which versions were at risk.

No details on how attackers are using the flaw, or whom they are targeting, have been shared by Apache. The same report credits a researcher named n0mi1k with the discovery and Matt Raible with the report. The CISA entry lists ransomware use as unknown.

Why deserialization bugs are so serious

Deserialization rebuilds live objects from data that arrived as text or bytes. If an application does this with attacker-supplied input, the attacker gets some say over which objects the program constructs. In Java applications that can escalate to running code on the server, which is why the CVSS vector rates confidentiality, integrity and availability impact as high.

What makes this case worse is the order of operations. Roller processes the request first and consults the XML-RPC setting afterward. As the advisory puts it, switching XML-RPC off in the administration UI does not help on older versions, because the request is already deserialized by the time that setting is read.

Who is affected

  • Any Apache Roller installation from 4.0.0 through 6.1.4, as listed in the advisory.
  • Instances where the /roller-services/xmlrpc path is reachable from the internet, since only network access is required.
  • Teams that followed only CVE-2026-82384 and concluded that versions other than 6.1.5 were safe.
  • Forgotten or lightly maintained Roller blogs on old subdomains, which are easy to miss in an inventory.
The research does not explain how 6.1.5 is treated under the broader CVE. The earlier record named 6.1.5, while the new one lists 4.0.0 through 6.1.4 and recommends 6.1.6 or later. Aim for 6.1.6 or newer whatever version you run today.

How to check your exposure

First, list every Roller instance you operate and note its version. Then see whether the XML-RPC servlet is mapped and how the extension setting is configured.

The following read-only search looks in web.xml for the servlet mapping and the extension setting named in the advisory. Run it on the server from the Roller deployment directory; any matching line shows where the endpoint is configured.

Search web.xml for the XML-RPC mapping and extension setting (run on the Roller server, read-only)Shell
grep -n -E 'roller-services/xmlrpc|enabledForExtensions' WEB-INF/web.xml

If the mapping is present and enabledForExtensions is not set to false on an affected version, treat the endpoint as exposed. Confirm the version from the admin interface or the deployed files and compare it with the range 4.0.0 through 6.1.4.

What to do now

  1. Inventory every Apache Roller instance and record its version.
  2. Upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.
  3. If you cannot upgrade right away, set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller.
  4. Do not count on the administration UI toggle for XML-RPC; older versions deserialize the request before checking it.
  5. Where practical, limit network access to the XML-RPC path with a firewall or reverse proxy rule until you are patched.
  6. Since exploitation is confirmed, review the server for signs of compromise (see the next section).
  7. If you find any sign of compromise, rotate credentials and secrets stored on or reachable from the Roller host.
Caution. Restarting Roller interrupts the blog while it reloads. Schedule a short maintenance window and keep a copy of the original web.xml before editing so you can compare changes.

Both interim mitigations are configuration edits. Change WEB-INF/web.xml as the advisory describes, either setting enabledForExtensions to false or removing the servlet mapping for /roller-services/xmlrpc, then restart Roller using your usual service or container procedure.

Detection and monitoring after patching

Upgrading shuts the door but does not show whether someone already got in. Apache has not published indicators of compromise, so rely on general investigation:

  • Search web server and application logs for requests to /roller-services/xmlrpc from before you patched, paying attention to unfamiliar sources or unusually large request bodies.
  • Look for unexpected child processes, new files, new scheduled tasks or outbound connections from the Java process running Roller.
  • Compare deployed files and configuration with a known-good copy or a clean install.
  • Follow the Apache project announcements and the CISA KEV entry for new details, since exploitation specifics are unpublished.

Outside-in tools help with the public side only. A free website malware scanner can check what your public pages serve, and certificate, DNS and header-change monitoring can flag unexpected changes. Neither can see inside the server, so they complement log review rather than replace it. If you suspect a breach, follow our guide on what to do when a website is hacked.

Timeline

Dates as stated in the research
DateEvent
September 2026CVE-2026-82384 patched, listing only Roller 6.1.5 as affected (per The Hacker News)
Nov 17, 2026Advisory published to the GitHub Advisory Database
Nov 18, 2026The Hacker News reports active exploitation, citing the Apache Software Foundation
Nov 20, 2026Added to the CISA KEV catalog with a listed due date of 2026-11-23

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-129448 - GitHub Advisory Databasegithub.com
  2. Apache Roller Deserialization of Untrusted Data Vulnerability (CVE-2026-129448) is being actively exploitednvd.nist.gov ·
  3. Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Requiredthehackernews.com ·
  • Apache Roller
  • RCE
  • deserialization
  • CISA KEV
  • XML-RPC