Apache says a critical flaw in Apache Roller, tracked as CVE-2026-129448, is being actively exploited. In its advisory of 17 November 2026, Apache lists Roller 4.0.0 through 6.1.4 as affected and recommends upgrading to 6.1.6 or later. If your Roller blog server is reachable from the internet, upgrade now, or apply the documented web.xml workaround and restart.
This guide covers what Apache and the reporting outlet said, how to decide whether you are affected, and what to do in order. It is defensive only and does not describe how to exploit the flaw.
What happened
The facts below come from the Apache advisory on the oss-security list (17 November 2026) and Apache Roller's own security and download pages. BleepingComputer reported the advisory on 18 November 2026.
| Date | What the source says | Source |
|---|---|---|
| 24 September 2026 | Apache Roller 6.1.6 released; Apache's security page lists it as fixing CVE-2026-82384, "Unauthenticated deserialization in the XML-RPC endpoint," rated Critical | Roller security page |
| 25 September 2026 | Advisory for CVE-2026-82384 posted to oss-security, listing Apache Roller 6.1.5 as affected and recommending 6.1.6 or later | oss-security |
| 17 November 2026 | New advisory for CVE-2026-129448: Apache Roller 4.0.0 through 6.1.4 are affected; Apache says the issue is the same vulnerability as CVE-2026-82384 and "is being actively exploited" | oss-security |
| 18 November 2026 | BleepingComputer reports the advisory | BleepingComputer |
According to the advisory, the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. That lets an unauthenticated remote attacker execute arbitrary code. Apache rates it Critical, CVSS 3.1 score 9.8 (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
What is confirmed and what is not
| Statement | Who made it | Status |
|---|---|---|
| The flaw is being actively exploited | Apache advisory | Stated by the vendor project |
| Who is exploiting it | Nobody has said | Unknown |
| How many servers are compromised | Nobody has said | Unknown |
| Indicators of compromise | None found in the advisory or the BleepingComputer report | None published |
| Listed in CISA's Known Exploited Vulnerabilities catalog | Not confirmed | We could not verify this; see "What we checked" |
The version wording differs between sources. The advisory header says "before 6.1.5," while its description says 4.0.0 through 6.1.4, and the September entry listed only 6.1.5. Apache's security page says users of earlier versions should also upgrade to 6.1.6. The practical reading is the same: anything older than 6.1.6 should be treated as vulnerable.
Am I affected?
You are in scope if you run Apache Roller, the open-source Java group-blogging server, at any version from 4.0.0 up to and including 6.1.5, and the application is reachable by an attacker. The advisory describes the attack as unauthenticated and remote, so a login page being protected does not help.
- Find your running Roller version from your own deployment records or the version shown by your installation. We did not find an official Roller page documenting a version-check command, so use whatever you normally use to track the release you deployed.
- If the version is older than 6.1.6, treat the server as vulnerable.
- Note that the XML-RPC servlet is mapped at
/roller-services/xmlrpc. Apache's September announcement says the servlet is mapped unconditionally, so the code path is reachable even when XML-RPC is disabled in settings.
No indicators of compromise (IP addresses, file hashes, payload samples) were published in the advisory or the BleepingComputer report as of 19 November 2026. We therefore do not list any. Absence of published indicators does not show that your server is clean.
What to do now
- Upgrade to Apache Roller 6.1.6 or later. Apache's download page lists 6.1.7 as the latest release, and its security page notes that 6.1.7 also addresses other issues. Apache says the fix in 6.1.6 disables the extension types and rejects XML-RPC requests when the feature is turned off.
- If you cannot upgrade immediately, apply the workaround from the advisory (below) and restart Roller.
- Reduce exposure while you work. If the blog does not need to be public today, take it offline or restrict access at your firewall or reverse proxy. This is general hardening, not an Apache instruction.
- Assume exploitation is possible if the server was internet-facing on an affected version. Review your access logs for requests to
/roller-services/xmlrpcand look for unexpected processes, files or outbound connections on the host. Because no indicators were published, this is a judgment call for your own incident process. - Rotate secrets the Roller process could reach (database credentials, API keys, service account passwords) if you find signs of compromise, and rebuild the host from a known-good image where you can.
- Report suspected vulnerabilities in Roller privately to [email protected], as Apache's security page asks. Do not use the public issue tracker or public mailing lists.
Step 1: Upgrade
Read the release notes, including the behavior changes, before upgrading a live site; Apache's download page says to do this. Then download the release and verify it. Apache's download page says to get the KEYS file and the .asc signature from the main distribution directory (downloads.apache.org/roller), not from a mirror, and to verify with GPG:
gpg --import KEYS
gpg --verify ${filename}.tar.gz.ascApache says you can instead verify the SHA-256 or SHA-512 checksum; Roller 6.1.7 ships .sha256 and .sha512 files. Take a backup of your database and configuration before the upgrade. For the upgrade procedure itself, follow the upgrade notes in the Roller documentation for your target release.
Step 2: The documented workaround
For administrators who cannot upgrade right away, the advisory says to do one of the following and then restart Roller:
- Set
enabledForExtensionstofalseinWEB-INF/web.xml. - Or remove the
/roller-services/xmlrpcservlet mapping.
Apache is explicit that disabling XML-RPC in the administration UI is not sufficient, because older versions deserialize the request before checking that setting. The advisory gives no other workaround. Apache's security page says security fixes ship in new releases and older releases are not patched in place, so the workaround is a bridge, not a fix.
How to protect yourself
- Stay on a supported release. Apache's security page says fixes arrive in new releases. Track the Roller security page and the oss-security list for announcements.
- Do not expose services you do not use. If you do not use XML-RPC clients, removing the servlet mapping (after upgrading, if your release still maps it) shrinks the attack surface. Check the 6.1.7 release notes before changing mappings.
- Run the application with least privilege. A code-execution flaw runs with the permissions of the Roller process, so limit what that account can read and where it can connect.
- Keep an inventory. Many teams run a Roller blog that nobody owns. List every Java web application you host, including internal blogs, so that a future advisory reaches the right person.
Checklist
- Version identified; anything older than 6.1.6 treated as vulnerable
- Backup taken
- Upgraded to 6.1.6 or later (6.1.7 is the latest per Apache's download page), signature or checksum verified
- If not upgraded:
enabledForExtensionsset tofalseor the XML-RPC mapping removed, and Roller restarted - Logs reviewed for requests to
/roller-services/xmlrpc - Credentials rotated if compromise is suspected
What we checked
- Opened the BleepingComputer report (18 November 2026) on 19 November 2026 and compared it with the Apache advisory; the CVE, the 4.0.0 through 6.1.4 range, the 6.1.6 fix and the workaround match.
- Opened the oss-security advisory posted 17 November 2026 on 19 November 2026: Critical, CVSS 3.1 score 9.8, "being actively exploited," same vulnerability as CVE-2026-82384.
- Opened the oss-security announcement of 25 September 2026 for CVE-2026-82384: affected version 6.1.5, fix 6.1.6, servlet mapped unconditionally.
- Opened Apache Roller's security page: CVE-2026-82384 fixed in 6.1.6 (released 24 September 2026), how to report privately. CVE-2026-129448 itself did not appear on that page.
- Opened Roller's download page: 6.1.7 is the latest release, with the GPG and checksum verification steps copied above. The page gave no release date.
- Version wording differs across the advisory header, its description and the September entry; we reported all three.
- Could not confirm whether CISA lists the CVE in its Known Exploited Vulnerabilities catalog; the page content we could read showed only part of the list.
- Not tested on a live Roller server; no official Roller page we opened documents a version-check command, so we did not give one.
Last tested: 2026-11-19
Sources
- Apache advisory for CVE-2026-129448 on oss-security: https://www.openwall.com/lists/oss-security/2026/11/17/5
- Apache advisory for CVE-2026-82384 on oss-security: https://www.openwall.com/lists/oss-security/2026/09/25/17
- Apache Roller security page: https://roller.apache.org/security.html
- Apache Roller downloads: https://roller.apache.org/downloads/downloads.html
- BleepingComputer report: https://www.bleepingcomputer.com/news/security/apache-warns-of-roller-rce-vulnerability-exploited-in-attacks/
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.