Threat feed

CVE-2026-129448 — Apache Roller unauthenticated deserialization through XML-RPC (CVSS 9.8, exploited, in CISA KEV): explainer and fix (upgrade to 6.1.6)

CVE-2026-129448: Apache Roller 4.0.0 to 6.1.5 runs attacker data through XML-RPC before login (CVSS 9.8). Exploited, in CISA KEV. Upgrade to 6.1.6.

Published 2026-11-21 Updated 2026-11-21 Last verified 2026-11-21 6 min read
On this page

For: anyone who runs Apache Roller (a Java multi-user blog server), and the IT staff or hosting contractors who look after it. This article is based on Apache's announcements, the CVE records in NVD and CISA's KEV data; it does not cover attack steps.

続報待ち:この記事は公式発表に合わせて更新します

Who is affected

anyone who runs Apache Roller (a Java multi-user blog server), and the IT staff or hosting contractors who look after it.

Confirmed so farSee the table ↓
  • The flaw
  • Affected versions
  • Fix and workaround
1 more
  • Exploitation
Not yet confirmed
  • Who is exploiting the flaw, since when and how widely (not published in Apache's announcement or the KEV entry)
  • Whether Apache publishes indicators or more guidance beyond the workaround
  • Any ransomware use (the KEV entry says Unknown)
What to do nowSee the steps ↓
  1. Find your Roller servers and check the version
  2. Apply Apache's workaround until you can upgrade
  3. Upgrade to Roller 6.1.6 or later
2 more
  1. Limit who can reach the server
  2. Check for signs of compromise
Where to verify (source)All sources ↓
Apache Roller
Last checked
as of November 21, 2026
Follow-up plans and what we checked

Apache announced CVE-2026-82384 in late September 2026 (Roller 6.1.5 only). On November 17 it published CVE-2026-129448 for Roller 4.0.0 through 6.1.4, said it is the same vulnerability, and said it is being actively exploited. CISA added it to the KEV catalog on November 20 with a federal due date of November 23 and flagged it for forensic triage. CISA's SSVC entry on the NVD record lists exploitation as active and the flaw as automatable. We do not know the scale of exploitation.

What to do today

1

Find your Roller servers and check the version

Look for Roller in your server inventory, application server (Tomcat and similar) deployments and reverse-proxy routes. Include test, old and unmaintained blogs. The version is shown in the application files and administration screens. Every release from 4.0.0 to 6.1.5 is affected; 6.1.6 or later is fixed.

2

Apply Apache's workaround until you can upgrade

Per Apache, set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Apache says disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. Tools that post to the blog through XML-RPC may stop working; that is the cost of the workaround (this site's reading).

3

Upgrade to Roller 6.1.6 or later

Per Apache, 6.1.6 disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. Back up the database and configuration first, then confirm the new version after the restart.

4

Limit who can reach the server

As a general measure, not Apache's: if the blog does not need to be public, or XML-RPC is used only from a known address, restrict access at the reverse proxy or firewall. Treat it as a stopgap, not a replacement for the steps above.

5

Check for signs of compromise

Because exploitation is confirmed and the start date is unknown, look back through the web server and application logs for unexpected requests to the XML-RPC path from unfamiliar sources, unexpected new files or processes on the server, and unexpected outbound connections. No finding does not prove you are clean. If something looks wrong, isolate the server and rotate the database and other credentials stored on it (how to check for intrusion).

What kind of flaw this is

Advisory summary — ADVISORY / exploited (CISA KEV)
CVE
CVE-2026-129448 (Apache Roller 4.0.0 to 6.1.4) and CVE-2026-82384 (Roller 6.1.5); same vulnerability per Apache
Severity
CVSS v3.1 9.8 (CRITICAL; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Type
Deserialization of untrusted data (CWE-502)
Impact
An unauthenticated remote attacker can execute arbitrary code (Apache)
Affected
Apache Roller 4.0.0 through 6.1.5
Fix
Roller 6.1.6 or later. Workaround: enabledForExtensions=false or remove the /roller-services/xmlrpc mapping, then restart (Apache)
Published
CVE-2026-82384: late September 2026. CVE-2026-129448: November 17, 2026
Exploitation
Actively exploited per Apache. In CISA KEV since November 20, due November 23
9.8
CVSS v3.1
6.1.6
First fixed Roller release
Nov 23
CISA KEV federal due date
0
Logins needed to reach the flaw
  • In short: the XML-RPC endpoint accepts vendor extension types and rebuilds objects from them before authentication. Handling untrusted input this way is the pattern described in insecure deserialization. We do not include request details.
  • Apache says the servlet is mapped unconditionally, so the data is processed even when the global XML-RPC feature is switched off. That is why the admin-screen setting does not help.
  • Our view: a blog server that has been installed once and left alone is exactly what this kind of flaw reaches. The practical task today is finding the servers, not reading the advisory.

What is known and what is not

ItemContentStatus
The flawUnauthenticated deserialization in the XML-RPC endpointConfirmed (Apache, NVD)
Affected versions4.0.0 to 6.1.4 (CVE-2026-129448) and 6.1.5 (CVE-2026-82384); same flawConfirmed (Apache)
Fix and workaround6.1.6 or later; web.xml setting or mapping removalConfirmed (Apache)
ExploitationActively exploited; in CISA KEV since November 20Confirmed (Apache, KEV)
Who, since when, how manyNot publishedUnknown
Ransomware useUnknown per the KEV entryNot stated

Sources

Attack steps and indicators of compromise (IOCs) are not included. Last verified: November 21, 2026.

Update history

2026-11-21: First report. Based on Apache's announcements, NVD records and the CISA KEV data.

Latest breaking reports

All breaking reports →

FAQ

QWhat is CVE-2026-129448?
A

A deserialization of untrusted data flaw (CWE-502) in Apache Roller. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester, so an unauthenticated remote attacker can execute arbitrary code. CVSS v3.1 is 9.8 (critical). Apache says it is the same vulnerability as CVE-2026-82384.

QWhich versions are affected, and what is the fix?
A

Apache lists Roller 4.0.0 through 6.1.4 under CVE-2026-129448, and Roller 6.1.5 under CVE-2026-82384, which Apache says is the same flaw. In practice every release from 4.0.0 to 6.1.5 is affected. Apache recommends upgrading to Roller 6.1.6 or later.

QIs there a workaround if I cannot upgrade yet?
A

Yes. Apache says to set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and then restart Roller. Apache also says that disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.

QIs it being exploited?
A

Yes. The Apache announcement for CVE-2026-129448 says the issue is being actively exploited, and CISA added it to its KEV catalog on 20 November 2026 with a federal due date of 23 November. Who is exploiting it and how widely have not been published.

QWhy are there two CVE numbers?
A

CVE-2026-82384 was announced in late September 2026 and listed only Roller 6.1.5 as affected. On 17 November 2026 Apache published CVE-2026-129448 to cover the earlier releases (4.0.0 through 6.1.4) and said it is the same vulnerability. Check both records for your version.

QI do not run Roller myself. Does this matter to me?
A

Only if a service you use or host runs it. Roller is a self-hosted blog server, so check your own and your contractors' servers for a Roller installation, including old ones that nobody has updated.