CVE-2026-129448 - Apache Roller Deserialization of Untrusted Data Vulnerability

CVE-2026-129448

Apache Roller - Pre-Auth RCE via XML-RPC Vendor Extension Deserialization

What is Apache Roller?

Apache Roller is a Java blog server, first released in 2002 and run as an Apache Software Foundation project since 2007. It is a self-hosted multi-user weblog platform that ships as a WAR deployed into Tomcat or a similar servlet container, backed by a relational database. The Apache Software Foundation runs its own blogs on it, and it turns up in universities, government sites and corporate intranets where somebody needed a blog that lives on their own infrastructure.

Among the legacy interfaces Roller carries is an XML-RPC endpoint at /roller-services/xmlrpc, which implements the Blogger, MetaWeblog and Atom publishing APIs so that desktop blogging clients such as the old Windows Live Writer can post entries remotely. That endpoint is the attack surface here. A Roller instance is typically a public web server, which makes it directly reachable, and a compromise gives code execution inside a servlet container that holds the site's database credentials.

Overview

CVE-2026-129448 is an unauthenticated deserialization flaw, CWE-502, in Roller's XML-RPC endpoint. The endpoint accepts XML-RPC vendor extension types and deserializes them before it authenticates the requester, so an attacker who can send an HTTP POST to /roller-services/xmlrpc can reach Java deserialization with attacker-controlled data and no credentials. Apache scored it 9.8 under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and the outcome is remote code execution as the servlet container user.

The confusing part is the CVE numbering. This is the same defect that Apache first disclosed in September 2026 as CVE-2026-82384, an advisory that listed only Roller 6.1.5 as affected. That range was wrong: the flawed behaviour reaches all the way back to Roller 4.0.0. CVE-2026-129448 was published on 2026-11-17 to cover 4.0.0 through 6.1.4, the versions the first advisory left out. Both CVEs are fixed by the same change, shipped in Roller 6.1.6. An administrator who read the September advisory, checked that they were not on 6.1.5 and moved on is exactly the person this second CVE is aimed at.

Apache's advisory states plainly that the issue is being actively exploited, without saying by whom or against what. CISA added it to the KEV catalog on 2026-11-20 with a 2026-11-23 deadline, and NVD's CISA SSVC assessment marks exploitation as active, automatable yes, technical impact total.

Affected Versions

Product Vulnerable Fixed
Apache Roller (this CVE) 4.0.0 through 6.1.4 6.1.6 or later
Apache Roller (CVE-2026-82384) 6.1.5 6.1.6 or later
Apache Roller 6.1.6, 6.1.7 Not affected; 6.1.7 released 2026-11-11 is current

NVD expresses the range for this CVE as versions from 4.0 up to but not including 6.1.5. Taken together with the earlier CVE, every Roller release before 6.1.6 is affected.

Technical Details

XML-RPC is a 1990s RPC protocol that carries typed values in XML. The standard type set is small and harmless: integers, strings, booleans, dates, base64, structs and arrays. The Apache XML-RPC machinery Roller builds on also supports vendor extension types, an optional extension that can carry serialized Java objects in the request. When that extension is enabled, parsing a request means deserializing whatever the client sent.

Roller enabled extension types and, critically, did that parsing before any authentication check ran. In plain terms, deserialization is the step that turns bytes back into live objects, and an attacker who controls those bytes can control which classes get constructed and which methods get invoked along the way. With a suitable gadget chain present on the classpath, that becomes code execution. Because the parse happens first, no account on the target is needed: a single unauthenticated POST is the whole attack. There is no second request, no chaining and no user interaction, which is why the CVSS complexity is low and CISA's SSVC entry calls it automatable.

There is a trap in the mitigation story. Disabling XML-RPC in Roller's administration UI does not protect a vulnerable version, because the request is deserialized during parsing, before the code that consults that setting runs. The fix in apache/roller PR 171, titled "Disable vendor extension types on the XML-RPC servlet", does two things: it sets enabledForExtensions to false so that only standard XML-RPC value types are accepted, and it adds a servlet filter that gates the endpoint on the webservices.enableXmlRpc property so that a disabled service is actually closed at the endpoint rather than merely ignored downstream.

Discovery

The researcher n0mi1k is credited with finding the flaw. Matt Raible, an Apache Roller committer, is credited with establishing that the affected range was far wider than the original advisory stated, which is what produced the second CVE ID. PR 171 was opened on 2026-08-29 and merged on 2026-09-05 by Dave Johnson (snoopdave), with review from Raible and Michael Bien.

Exploitation Context

Apache's advisory says the issue is being actively exploited and provides no further detail: no threat actor, no campaign name, no victim count, no first-observed date. CISA's KEV entry does not record ransomware use. No vendor or research organisation has published exposure counts for internet-facing Roller instances, and no one has publicly attributed the activity.

What raises the risk materially is that the fix has been public in a GitHub pull request since 2026-09-05, and public proof-of-concept and scanner code for this CVE has since appeared on GitHub. The patch diff tells an attacker exactly which endpoint and which setting mattered, and unauthenticated Java deserialization is a well-worn exploitation path. Treat any unpatched, internet-reachable Roller instance as presumptively compromised rather than merely exposed. The ten-week gap between the 6.1.6 release and this CVE means many operators have been exposed without knowing it, which is likely why CISA assigned a three-day deadline.

Remediation

  1. Upgrade to Apache Roller 6.1.6 or later. 6.1.7, released 2026-11-11, is the current release and is the better target. The BOD 26-04 deadline is 2026-11-23.
  2. If you cannot upgrade immediately, apply Apache's workaround: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping entirely if you do not use remote blogging clients. Restart Roller afterward; the change does not take effect until the container reloads.
  3. Do not rely on the administration UI toggle. Disabling XML-RPC there does not protect a pre-6.1.6 version, because the deserialization happens before that setting is consulted.
  4. Block or filter POST requests to /roller-services/xmlrpc at the reverse proxy or WAF as a stopgap, and restrict the endpoint to known client addresses if your users genuinely need it.
  5. Review access logs for POST requests to /roller-services/xmlrpc, especially from unfamiliar addresses, with unusual content lengths, or sent in bursts. Because exploitation needs only one request, a single suspicious POST is enough to warrant investigation.
  6. If you find evidence of exploitation, assume code execution as the servlet container user: look for new or modified files under the Roller webapp directory, unexpected child processes of the container, new scheduled tasks and outbound connections, then rotate the Roller database credentials and any other secrets stored in the container's configuration.
  7. Patch even if you believe you addressed CVE-2026-82384 in September. If you concluded you were unaffected because you were not running 6.1.5, that conclusion was based on an incorrect version range and you are probably still vulnerable.

Key Details

PropertyValue
CVE ID CVE-2026-129448
Vendor / Product Apache - Roller
NVD Published2026-11-17
NVD Last Modified2026-11-20
CVSS 3.1 Score9.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SeverityCRITICAL
CWE CWE-502 find similar ↗
CISA KEV Added2026-11-20
CISA KEV Deadline2026-11-23
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-23. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2026-08-29apache/roller PR 171 opened to disable XML-RPC vendor extension types
2026-09-05Fix merged to master
2026-09-24Apache Roller 6.1.6 released with the fix; the defect is disclosed as CVE-2026-82384 covering 6.1.5 only
2026-11-11Apache Roller 6.1.7 released
2026-11-17CVE-2026-129448 published, extending the affected range back to 4.0.0 and noting active exploitation
2026-11-20Added to CISA Known Exploited Vulnerabilities catalog
2026-11-23CISA BOD 26-04 remediation deadline