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 ↓
- Find your Roller servers and check the version
- Apply Apache's workaround until you can upgrade
- Upgrade to Roller 6.1.6 or later
2 more
- Limit who can reach the server
- 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
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.
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).
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.
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.
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
- 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
- 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
| Item | Content | Status |
|---|---|---|
| The flaw | Unauthenticated deserialization in the XML-RPC endpoint | Confirmed (Apache, NVD) |
| Affected versions | 4.0.0 to 6.1.4 (CVE-2026-129448) and 6.1.5 (CVE-2026-82384); same flaw | Confirmed (Apache) |
| Fix and workaround | 6.1.6 or later; web.xml setting or mapping removal | Confirmed (Apache) |
| Exploitation | Actively exploited; in CISA KEV since November 20 | Confirmed (Apache, KEV) |
| Who, since when, how many | Not published | Unknown |
| Ransomware use | Unknown per the KEV entry | Not stated |
Sources
- Apache Roller — CVE-2026-129448 announcement (November 17; versions, fix, workaround, active exploitation)
- Apache Roller — CVE-2026-82384 announcement (Roller 6.1.5; the original announcement)
- Apache Roller — CVE-2026-129448 vendor advisory (the advisory cited in the KEV entry)
- NVD — CVE-2026-129448 and CVE-2026-82384 (CVSS, CWE, KEV fields)
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 20, due November 23)
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.