Apache Roller: XML-RPC deserialization RCE (CVE-2026-129448, CVE-2026-82384) reported exploited; fixed in 6.1.6
CVE-2026-129448 CVE-2026-82384
Published 17/11/2026 18:56
Timeline
3 events over 6 d 1 h
- 11/11/2026 17:12UnconfirmedCommunity post+5 d 7 h
- 17/11/2026CorroboratedVulnCheck KEV+17 h
- 17/11/2026 18:56Published on WatchtowerPro CISO
In short
An attacker with network access to a Roller server can send a crafted XML-RPC request and run code on it without logging in. Apache Roller 4.0.0 through 6.1.5 is affected, and exploitation is reported. Update to 6.1.6 or later, ideally the current 6.1.7. Turning XML-RPC off in the admin UI does not protect older versions. GreyNoise reports a public exploit for CVE-2026-129448 (18/11/2026).
How bad is it
Critical. An attacker who can reach a vulnerable Roller server over the network can run their own code on it, without logging in.
No exploitation reported yet.
Severity score
The worst of 2 CVEs · CVSS 3.1 from NVD, from apache.org, read 18/11/2026.
What an attacker needs
- Internet access to itEnough
- A loginNot needed
- A user to clickNo
- Special settingsNo
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Run their own code on the system
- Read the data it holds
- Change or delete that data
- Take it offline
Type: remote code execution.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- Apache Roller versions 4.0.0 through 6.1.4 are listed as affected by CVE-2026-129448.
- CVE-2026-82384 lists Apache Roller 6.1.5 as affected. Together the two records cover 4.0.0 through 6.1.5; both name 6.1.6 as the fix, so 6.1.5 should be treated as affected.
- Default settings are exposed: the servlet is mapped unconditionally, so requests are parsed even when XML-RPC is disabled and no non-default configuration is needed.
- Turning XML-RPC off in the admin UI does not help, because older versions deserialize the request before checking that setting.
Fixed in
- 6.1 branch: 6.1.6 (named in both CVE records as the fix)
- Apache Roller 6.1.7 was announced by the Apache Roller PMC on 11/11/2026 as fixing 15 security advisories, and the PMC recommends every installation upgrade to it. The excerpt read does not say whether the XML-RPC flaw is among them. Some changes in 6.1.7 affect existing sites, so read the release notes first.
What to do now
- Update Apache Roller to 6.1.6 or later. It disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.
- If you cannot update at once, set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller.
- Optionally block the path /roller-services/xmlrpc at your reverse proxy or WAF if you can. This is a third-party suggestion and will break XML-RPC blog clients.
- These interim measures reduce exposure and do not make a server safe; only the update does. Treat 6.1.5 as vulnerable too.
- Because exploitation is stated by the CVE text, ask your hosting provider to check servers for compromise. The sources read give no indicators of compromise.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 6 open questions, followed up as sources answer and all 5 sources with their dates. And technology matching: which of your systems run Apache Roller, at which version, fixed or not - and what each one needs.
Main sources
Apache Roller: 15 CVEs fixed in 6.1.7 Research · Known exploited (VulnCheck KEV): Apache Software Foundation Apache Roller - Apache roller Deserialization of Untrusted Data Research · CVE-2026-129448: Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5) Research