Apache Roller · CVE-2026-129448 · CVE-2026-82384
Roller XML-RPC
Patch nowApache says exploited. No login. Fixed in 6.1.6.
A bug in Apache Roller, a Java blog server, lets anyone who can reach the site send one crafted request to its XML-RPC address and, in the worst case, run their own code, without logging in. Default installs from 4.0.0 through 6.1.5 are affected, even with XML-RPC switched off. Apache rates it Critical (CVSS 9.8) and says it is being actively exploited; one researcher's public code reaches the bug but says running code on a stock, up-to-date setup needs extra work. 6.1.6 (24 Sep 2026) and later fix it.
How scary is it?
Are you affected? only if all are true
1Roller 4.0.0 to 6.1.5
It's one bug with two CVEs: CVE-2026-129448 covers 4.0.0 through 6.1.4, and CVE-2026-82384 (25 Sep 2026) covers 6.1.5. 6.1.6 and later are fixed. Some news sites name 6.1.5 as the fix; Apache says 6.1.6.1,2,4
2XML-RPC extensions still oncommand
Every release up to 6.1.5 ships with enabledForExtensions set to true and /roller-services/xmlrpc mapped, so default installs are exposed. Turning XML-RPC off in the admin settings (off by default) does not help. Run this in Roller's webapp folder; <param-value>true</param-value> means exposed.1,2,7,8
grep -A1 enabledForExtensions WEB-INF/web.xml3Attackers can reach the site
One web request to /roller-services/xmlrpc is enough. No login and no user action are needed.1,3
What to do
1Upgrade to Roller 6.1.7
6.1.6 (24 Sep 2026) fixes this bug; 6.1.7 (11 Nov 2026) is the newest and also fixes CVE-2026-123374, a separate deserialization bug in ping responses. Read the 6.1.7 behaviour changes first: for example, Planet is now off by default. Apache doesn't patch older lines.4,5,6,12,13
Latest safe versions checked 20 Nov
2Can't upgrade yet?
In WEB-INF/web.xml, set enabledForExtensions to false, or remove the /roller-services/xmlrpc servlet mapping. Then restart Roller. The admin-screen switch alone is not enough.1
3Look for signs of attack
Attacks are POST requests to /roller-services/xmlrpc. Apache hasn't published other signs, attacker details or how many sites were hit. If you were exposed, check the server for changes you didn't make.1,10
This page shows you how to check. It can't tell you you're safe.
Sources (13) and changelog
- Apache: CVE-2026-129448 advisory, 4.0.0-6.1.4, actively exploited 17 Nov
- Apache: CVE-2026-82384 advisory, 6.1.5, default setup affected 25 Sep
- CVE record: CVSS 9.8, no login; CISA SSVC exploitation none (18 Nov) 17 Nov
- Apache Roller: security page, 6.1.6 and 6.1.7 release dates and fixes
- Apache Security: Roller advisories, CVE-2026-123374 fixed in 6.1.7
- Apache Roller GitHub: the fix (PR #171) 5 Sep
- Roller 6.1.5 source: extensions on, XML-RPC endpoint always mapped
- Roller 6.1.5 source: XML-RPC setting off by default
- CISA KEV catalog: not listed (18 Nov release)
- Tuxshin Security: public PoC, scanner and lab; RCE needs a gadget chain 18 Nov
- Public PoC for CVE-2026-82384 (6.1.5) 28 Sep
- Apache Roller: 6.1.7 changes and behaviour changes
- Apache Roller: downloads, 6.1.7 is the current release
- Published.