Actively exploited CVSS 9.8 Security news
Exploited Apache Roller flaw CVE-2026-129448 lets attackers run code through XML-RPC before logging in
On Tuesday 17 November 2026 the Apache Roller project said attackers are actively exploiting CVE-2026-129448, a flaw in the XML-RPC interface of its Java blogging platform. The endpoint deserialises data from the request before it checks who sent it, so an attacker with no account can run code on the server. It is the same bug as September's CVE-2026-82384, which listed only version 6.1.5 – it is now clear that every release since 4.0.0 is affected. The fix is in 6.1.6 and later.
Key points
- Who is affected: anyone running blogs or company sites on Apache Roller, the open-source Java blogging platform, typically deployed on Tomcat.
- The bug: the XML-RPC endpoint deserialises vendor extension types before it authenticates the caller (CWE-502), giving an unauthenticated attacker code execution.
- Watch out: turning XML-RPC off in the admin UI does not help – older versions deserialise the request before they check that setting.
- Exploitation: Apache says so in both the advisory and the CVE record, but has not shared details on the attacks, the attackers or the number of victims.
Vulnerabilities: CVE-2026-129448
What happened
On Tuesday 17 November 2026 the Apache Roller project sent out a security advisory for CVE-2026-129448 stating that the flaw is being actively exploited. Apache did not say who is behind the attacks, who is being targeted or how many servers have been compromised. An NVD record appeared the same day with a CVSS 3.1 score of 9.8 assigned by Apache.
This is not a brand-new bug. In September 2026 Apache published CVE-2026-82384 with the same description, but that record listed only version 6.1.5 as vulnerable. The new advisory widens the scope to every release since 4.0.0. Admins who decided in September that they were not affected because they were not on 6.1.5 have been exposed all along.
Technical details
Details come from Apache's advisories, the NVD record and the fix on GitHub. We do not publish exploitation instructions.
- Component: the XML-RPC endpoint (
/roller-services/xmlrpc) that desktop blogging clients use to talk to the blog (MetaWeblog and Blogger APIs). - Bug class: deserialisation of untrusted data (CWE-502). Roller's XML-RPC library accepted non-standard vendor extension types, which are deserialised while the request is parsed – before the caller is authenticated.
- Preconditions: no login and no special configuration. The servlet is always mapped, so requests are parsed even when XML-RPC is turned off in the blog settings.
- Impact: code execution on the server with the privileges of the application server running Roller (vector
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). - The fix (PR #171, merged 5 Sep 2026): disables extension types (
enabledForExtensions=false) and adds a filter that rejects XML-RPC requests when the feature is switched off.
Who is affected
| Apache Roller version | Status | Source |
|---|---|---|
| 4.0.0–6.1.4 | vulnerable | CVE-2026-129448 (17 Nov 2026) |
| 6.1.5 | vulnerable | CVE-2026-82384 (September 2026) |
| 6.1.6 and later | fixed | advisories for both CVEs |
| 6.1.7 | current release | project downloads page |
The NVD record for CVE-2026-129448 gives the range as "4.0.0 up to but not including 6.1.5"; combined with September's record for 6.1.5, everything up to and including 6.1.5 is vulnerable.
How to tell if you were compromised
Apache has not published indicators of compromise. What we recommend checking (our own advice, not project guidance):
- Access logs on the application server or reverse proxy:
POST /roller-services/xmlrpcrequests from addresses that are not your authors, especially if you never use XML-RPC. - Request bodies (if you log them or a WAF sees them): types from the Apache XML-RPC extensions namespace (
http://ws.apache.org/xmlrpc/namespaces/extensions) – normal blogging clients do not send them. - Child processes of the Java (Tomcat) process: shells,
curl,wget,powershell, and new outbound connections. - Files: new or modified JSP and JAR files in the application directory and
webapps, and new scheduled tasks under the service account.
You can break down the CVSS vector in our CVSS calculator.
What to do
- Upgrade to Apache Roller 6.1.6 or later (6.1.7 is current). The project recommends reading the release notes before upgrading a live site.
- If you cannot upgrade right away: set
enabledForExtensionstofalseinWEB-INF/web.xml, or remove the/roller-services/xmlrpcservlet mapping, then restart Roller. Disabling XML-RPC in the admin UI alone is not enough. - Restrict access to
/roller-services/xmlrpcat your reverse proxy or WAF to the addresses you publish from – if you do not use XML-RPC, block it entirely. - After patching, review logs and the server as described above. If you suspect compromise, assume the attacker could read the database credentials in Roller's configuration and rotate them.
Timeline
Updates
- 18 Nov 2026 – first version of this article.
FAQ
XML-RPC is disabled in my Roller admin settings. Am I protected?
No. The advisory explicitly says disabling XML-RPC in the UI is not enough: the servlet is always mapped and older versions deserialise the request before checking the setting. Only the upgrade or the web.xml change described under What to do closes the hole.
Why are there two CVE numbers for one bug?
September's CVE-2026-82384 listed only version 6.1.5 as vulnerable. On 17 Nov 2026 Apache issued CVE-2026-129448 for 4.0.0 to 6.1.4 and both records say it is the same vulnerability. In practice: everything from 4.0.0 to 6.1.5 is vulnerable, and 6.1.6 and later are fixed.
Is it in the CISA KEV catalog?
Not as of 18 Nov 2026 – we did not find it in catalog version 2026.11.17. But the exploitation warning comes from the Apache Roller project itself, which is reason enough to patch immediately.
Has Apache published indicators of compromise?
No. The advisory contains no IP addresses, hashes or sample requests. The checks under How to tell if you were compromised are our own recommendations, not project guidance.
Sources
- Apache Roller – CVE-2026-129448: Unauthenticated deserialization in XML-RPC endpoint (advisory, 17 Nov 2026)
- Apache Roller – CVE-2026-82384: Unauthenticated deserialization in XML-RPC endpoint (advisory, September 2026)
- NVD – CVE-2026-129448 (CVSS 3.1 9.8 by Apache, CWE-502)
- GitHub apache/roller – PR #171: Disable vendor extension types on the XML-RPC servlet
- Apache Roller – downloads (current release 6.1.7)
- BleepingComputer – Apache warns of Roller RCE vulnerability exploited in attacks (18 Nov 2026)
Spotted a mistake? Let us know and we will correct it openly.