What Apache says is wrong
Apache's advisory describes a classic deserialization bug (CWE-502). The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. In plain terms, the server processes attacker-controlled data before it checks who is sending it. That is the worst order of operations in security.
The CVE record's CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N is a bleak combination. It means the flaw is reachable over the network, needs no special conditions and needs no login or user interaction. Impact on confidentiality, integrity and availability is rated high.
Which versions are affected
The advisory says Apache Roller versions 4.0.0 through 6.1.4 are vulnerable. The version picture is slightly messy, so read this part carefully.
- CVE-2026-129448 is described as the same vulnerability as CVE-2026-82384, which listed only 6.1.5.
- The affected-version text in the newer record names versions through 6.1.4, but the earlier identifier covers 6.1.5.
- The fixed version is 6.1.6.
- Some aggregator sites list 6.1.5 as the fix. Apache's own remediation text says 6.1.6 or later.
Don't treat 6.1.5 as safe. The earlier CVE listed it as affected, and Apache points to 6.1.6 for the remedy.
What has not been disclosed
Apache confirms exploitation in the wild. BleepingComputer reports that Apache has not said who is behind the attacks or how many servers are compromised. I found no public incident counts or attribution. I also found no confirmation that CISA has added this CVE to its Known Exploited Vulnerabilities catalog, so don't assume it has.
Public exploit-tracking sites already list a proof-of-concept entry for the CVE. I haven't verified that code. If you run Roller, assume attackers know the endpoint path.
What the fix changes
The upstream change is pull request #171, "Disable vendor extension types on the XML-RPC servlet". It was merged on September 5, 2026 and labeled for 6.1.6. Its description says Roller's XML-RPC servlet accepted the library's non-standard vendor extension types, which Roller doesn't use. It also says the mapped endpoint answered requests even when the XML-RPC feature was switched off.
The fix does two things:
- It disables the extension types, so the dangerous deserialization path is closed.
- It gates the endpoint on the
webservices.enableXmlRpcsetting. A disabled service is then not reachable and doesn't read request bodies.
Ordinary XML-RPC calls keep working when the feature is enabled. Per the pull request's tests, with the toggle on, an extension-type value is rejected while a normal call reaches its handler.
This explains Apache's warning about the admin UI. On older builds, the endpoint is mapped and parses the request before any per-handler check. Unchecking the XML-RPC box in the admin screen therefore doesn't protect you.
What to do
Preferred fix: upgrade to Apache Roller 6.1.6 or later using the project's normal installation and release procedures. Confirm the deployed version afterward instead of assuming the upgrade took.
If you can't upgrade immediately, Apache lists two temporary mitigations. Both need a Roller restart:
- Set
enabledForExtensionstofalseinWEB-INF/web.xml. - Remove the
/roller-services/xmlrpcservlet mapping.
Some caveats:
- Removing the mapping will break any desktop blogging clients or integrations that use XML-RPC. The pull request's reviewers noted that some clients, such as MarsEdit, can show confusing errors when the endpoint is closed.
- Apache gives no deployment-specific file-edit steps beyond these changes, so work from your own installation layout.
- These are stopgaps, not a substitute for the patched release.
A practical checklist
- Find every Roller instance, including forgotten internal blogs, team sites and test servers.
- Check each version against the 4.0.0 to 6.1.5 range.
- Check whether
/roller-services/xmlrpcis reachable from the internet or from untrusted network segments. - Upgrade to 6.1.6 or later. If you can't, apply a mitigation and restart.
- If the server was exposed and unpatched, treat it as potentially compromised. Review web and application logs for unusual XML-RPC POST requests, and check for unexpected processes, files and outbound connections.
One monitoring tip from a security news site, The Hacker Wire, is to look for odd request sizes and unexpected data types in XML-RPC payloads. That is general guidance, not a confirmed indicator of compromise for these attacks.
The bigger picture
This flaw is a reminder that small, forgotten internet-facing apps are often the easiest way in. Few people watch niche software, and it tends to sit unpatched. Deserialization bugs are also a recurring Java problem: parsing untrusted data before authentication keeps coming back in new forms.
Roller's market share is small, so the number of exposed servers may be modest. That is an inference, not a measured figure. But a 9.8-rated, unauthenticated, actively exploited bug is worth an immediate inventory check even if you think you don't run it.
References
- Apache warns of Roller RCE vulnerability exploited in attacks BleepingComputer · 2026-11-18T05:35:05-05:00
- CVE-2026-129448: Apache Roller RCE Actively Exploited, Patch Now securityonline.info
- OSV - Open Source Vulnerabilities osv.dev