Our Thinking / Field Notes / The Security Watch

EVOLVING SECURITY ADVISORY / APACHE ROLLER CVE-2026-129448 UNAUTHENTICATED DESERIALIZATION IN XML-RPC

Apache Roller Remote Code Execution Flaw Exploited: What To Do

CVE-2026-129448 lets an unauthenticated attacker run code on Apache Roller servers via the XML-RPC endpoint. Apache says it is exploited and CISA lists it. Here is how to check exposure, upgrade, mitigate and look for compromise.

What matters now

Current position: Critical (CVSS 3.1 base score 9.8). Unauthenticated remote code execution through the XML-RPC endpoint.

Affected versions: Apache Roller 4.0.0 through 6.1.5 (CVE-2026-129448 covers 4.0.0 to 6.1.4; the same bug as CVE-2026-82384, which covers 6.1.5). Fixed in 6.1.6 or later; 6.1.7 is current.

Observed exploitation: Actively exploited according to Apache's advisory; added to the CISA Known Exploited Vulnerabilities catalogue on 20 November 2026 (federal due date 23 November 2026; CISA lists ransomware use as unknown). Attack details and indicators of compromise have not been published.

Recommended next action: Upgrade to Apache Roller 6.1.7 (fix for this flaw is 6.1.6 or later). If you cannot upgrade immediately, set enabledForExtensions to false in WEB-INF/web.xml or remove the /roller-services/xmlrpc servlet mapping and restart; disabling XML-RPC in the admin UI is not sufficient. Check logs and the server for signs of compromise.

Identifiers: CVE-2026-129448, CVE-2026-82384

Immediate guidance

If you run Apache Roller 4.0.0 through 6.1.5, treat the server as exposed to CVE-2026-129448, an unauthenticated remote code execution flaw that Apache says is being actively exploited and that CISA added to its Known Exploited Vulnerabilities catalogue on 20 November 2026. Upgrade to Roller 6.1.7 (Apache's fix for this flaw is 6.1.6 or later; 6.1.7 is the current release). If you cannot upgrade today, set enabledForExtensions to false in WEB-INF/web.xml or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. Switching XML-RPC off in the Roller admin screens does not protect older versions. Because exploitation is confirmed, also check whether the server has already been compromised.

Current risk: who is affected and how serious it is

The flaw is tracked as CVE-2026-129448 and scores 9.8 (critical) on CVSS 3.1. Roller's XML-RPC endpoint accepts a set of optional vendor extension data types and unpacks them before it has checked who is calling. A remote attacker needs no account, no password and no user interaction to abuse that and run code on the server. In practice that means one crafted request to a public URL.

Apache's advisory, last updated on 17 November 2026, says the issue is being actively exploited. CISA added it to the Known Exploited Vulnerabilities catalogue on 20 November 2026, with a due date of 23 November 2026 for US federal agencies, and marks the entry as requiring forensic triage. UK organisations are not bound by that deadline, but it is a fair indication of how quickly the issue should be treated. CISA lists known ransomware use as unknown. Apache has not published details of the attacks, who is behind them or how many servers are affected, so nobody outside Apache and the victims can say yet what attackers do after getting in.

The version range needs a careful reading. The advisory for CVE-2026-129448 says Apache Roller 4.0.0 through 6.1.4. The same bug was first published as CVE-2026-82384, which listed only 6.1.5. Apache's advisory page confirms the two are the same vulnerability, so the sensible reading is that every release from 4.0.0 to 6.1.5 is affected and 6.1.6 is the first fixed release. Apache's own page is inconsistent about the upper bound, which is another reason not to rely on being on 6.1.5 as a safe point.

  • Affected: Apache Roller 4.0.0 through 6.1.5 (CVE-2026-129448 covers 4.0.0 to 6.1.4; CVE-2026-82384 covers 6.1.5).
  • Fixed: 6.1.6 or later for this flaw. 6.1.7 is the current release and also fixes a further set of issues.
  • Exposure: any Roller instance where the XML-RPC endpoint can be reached, which includes any public blog served from the normal web application path.
  • Exploitation: confirmed by Apache's advisory and by CISA's catalogue listing. Attack details and indicators of compromise have not been published.

Find out whether you run Roller and which version

Roller is often installed once and then forgotten, so start by finding every instance. Look for Java web applications called roller (or similar) on your Tomcat or other servlet container servers, and ask whoever looks after your internal blogs, team sites or documentation portals if they run on Roller. Internet-facing instances come first.

You need to know the exact version. Roller's authoring pages normally show it in the footer; otherwise check the name of the package that was deployed. If you cannot establish the version quickly, treat the instance as affected.

  1. Make a list of every server running a Roller web application, noting which ones are reachable from the internet and which only from your internal network.
  2. For each one, record the version. Anything from 4.0.0 to 6.1.5 is vulnerable; 6.1.6 and later contain Apache's fix for this flaw.
  3. On any server you can reach by shell, read the current setting in the deployed web.xml. Replace YOUR_ROLLER_WEBAPP_PATH with the folder where Roller is deployed, for example inside your Tomcat webapps directory. This command only reads the file and changes nothing.
    bash
    grep -n -i "enabledForExtensions" YOUR_ROLLER_WEBAPP_PATH/WEB-INF/web.xml

Upgrade to Roller 6.1.7

Upgrading is the fix. Apache's advisory says 6.1.6 disables the extension types and rejects XML-RPC requests when the feature is turned off, and 6.1.7, released on 11 November 2026, is the current release on the Roller downloads page. It addresses a further batch of issues, including another deserialization flaw (CVE-2026-123374) that affects versions up to and including 6.1.6. If you are going to restart the application anyway, go straight to 6.1.7 rather than stopping at 6.1.6.

The downloads page advises reading the release notes, including behaviour changes, before upgrading a live site, so do that before you touch production. The upgrade restarts the application, so the blog will be briefly unavailable. Take a database backup and a copy of your Roller configuration and uploaded media first, so you can roll back if the upgrade misbehaves. Roller's upgrade procedure and any database migration steps are in the release notes and installation guide for your version, so follow those rather than improvising.

  1. Read the release notes (CHANGES.md for 6.1.7) and note any behaviour changes that affect your site.
  2. Download 6.1.7 from the Apache Roller downloads page, taking the checksum and signature files from Apache's main site rather than a mirror, and verify the download.
  3. Back up the Roller database, your configuration and any uploaded media. Confirm you can read the backup before going further.
  4. Where possible, rehearse the upgrade on a non-production copy, then apply it to the live server following the upgrade instructions in the release notes. Plan for the application to be offline while it restarts and migrates.
  5. Confirm the new version is shown in the Roller authoring page footer or the deployed package, that the site loads and that you can sign in and publish a test entry.
  6. If you use desktop blogging clients that talk to Roller over XML-RPC, check they still connect after the upgrade.

If you cannot upgrade today: a temporary mitigation

Apache documents two stopgaps for older versions. Either set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping so the endpoint is not served at all. Both need a Roller restart to take effect. The fix in Apache's code change simply turns the vendor extension types off, because Roller itself only uses the standard XML-RPC value types, so the first option should not affect normal use. Removing the mapping is stronger but will break any desktop blogging client that uses XML-RPC.

The trap is the admin screen. Turning XML-RPC off under Roller's administration settings does not protect older versions, because they deserialize the request before they check that setting. A site where XML-RPC is already disabled in the UI is still vulnerable.

As an additional layer, and as our own engineering judgement rather than something Apache prescribes, you can block external requests to /roller-services/xmlrpc at your reverse proxy or web application firewall. That reduces exposure while you schedule the upgrade but does not replace the upgrade, and an attacker already on your internal network could still reach the application.

  1. Take a copy of web.xml so you can revert if needed.
  2. Open WEB-INF/web.xml in the deployed Roller application. Find the setting named enabledForExtensions in the XML-RPC servlet definition and set it to false. Alternatively, remove the servlet mapping for /roller-services/xmlrpc.
  3. Restart Roller (or the servlet container hosting it) so the change is loaded. Expect a short outage.
  4. Re-run the read-only check from earlier to confirm the file now contains the value you set.
    bash
    grep -n -i "enabledForExtensions" YOUR_ROLLER_WEBAPP_PATH/WEB-INF/web.xml
  5. Treat this as a holding position only. Schedule the 6.1.7 upgrade and do not assume the instance is safe because the mitigation is in place.

Check whether the server has already been compromised

Because exploitation is confirmed and the bug needs no login, patching only closes the door. It does not tell you whether someone has already walked through it. CISA's catalogue entry marks forensic triage as required, and no indicators of compromise have been published, so the checks below are generic good practice for a server that may have run attacker code rather than a Roller-specific signature list.

Legitimate XML-RPC clients also use this endpoint, so a request to it is not proof of an attack. You are looking for requests from addresses you do not recognise, unusually large request bodies, and anything that changes around the same time as those requests. Do the log review before you rebuild or wipe anything, so you keep the evidence.

  • Web server or Tomcat access logs: look for POST requests to /roller-services/xmlrpc from unfamiliar addresses, especially in the period before you applied a fix.
    bash
    grep -h "POST /roller-services/xmlrpc" YOUR_ACCESS_LOG_FILES
  • Processes and services: check for unexpected child processes, scheduled tasks or services started by the account that runs Roller or Tomcat.
  • Files: look for recently created or modified files in the web application directories and temporary folders that you cannot account for.
  • Accounts and secrets: look for new Roller administrator accounts or unexpected changes, and treat database credentials and any other secrets stored in the Roller configuration as exposed if you find evidence of compromise.
  • Outbound traffic: check for unexpected connections from the server to the internet.

If you find signs of compromise

Stop and treat it as an incident. Preserve the logs and a disk or snapshot image before changing anything, isolate the server from the network if you can do so safely, and involve whoever handles incident response for your organisation. A server that has run attacker code cannot be reliably cleaned by patching alone: the safest route is usually to rebuild from a known good state on 6.1.7, restore content from a backup taken before the compromise, and rotate the database password and any credentials the server could read. Check whether the same credentials are used elsewhere and whether the server can reach other systems.

If the incident involves personal data, you may have reporting obligations under UK data protection law, so involve whoever handles that for your organisation early.

What is still unknown

Apache and CISA have not published the techniques used in the attacks, the post-exploitation behaviour or any indicators of compromise, and ransomware use is listed as unknown. This article will need updating if that changes. Until then, base your decisions on the confirmed facts: the flaw needs no authentication, it is exploited, and 6.1.6 and later contain Apache's fix.

Update history

We’ll keep this page updated as new information becomes available. Check back for the latest developments.

  1. 21 November 2026: Initial update. Apache's advisory (updated 17 November) states CVE-2026-129448 is actively exploited, and CISA added it to the Known Exploited Vulnerabilities catalogue on 20 November 2026 with a 23 November 2026 due date. Apache recommends 6.1.6 or later; 6.1.7 is the current release. Update source

Technical terms explained
deserialization
Turning received data back into live objects inside a program. If the program does this before checking the data is trustworthy, crafted input can make it run code the attacker chose.
forensic triage
A quick, structured look at logs, files and running activity to decide whether a system has been compromised and what to preserve before anyone rebuilds it.
Known Exploited Vulnerabilities
A catalogue maintained by the US agency CISA of vulnerabilities with evidence of exploitation in real attacks. Listing means exploitation has been seen; it does not by itself identify who was attacked.
remote code execution
A flaw that lets an attacker run their own commands or programs on a system from elsewhere on the network.
reverse proxy
A server that sits in front of a web application and passes requests through to it, which lets you block or filter particular URLs before they reach the application.
XML-RPC
An older web protocol that lets software, such as desktop blogging clients, call functions on a server by sending XML over HTTP. Roller exposes it at /roller-services/xmlrpc.

Sources and further reading

KEEP THE CONVERSATION GOING

Not sure whether you run Roller, or what it can reach?

If you need help finding Roller instances, checking exposure, planning the upgrade or reviewing a server for signs of compromise, we can help.

Talk to Rismor