Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-129448: Unauthenticated XML-RPC Deserialization RCE in Apache Roller

Published Nov 17, 2026 · Updated today
Trending this week#22of 429,805 vulnerabilities
Mention activity · 30 days47 mentions · peak 33 in a dayToday
CVSS9.8Critical · v3.1
EPSS1.6%77th percentile
CISA KEVNoNot listed
In the wildReported13 exploitation records in Mallory
Vendor
Apache Software Foundation
IdentifiersCVE-2026-129448CWE-502 · Deserialization of Untrusted Data

CVE-2026-129448 is an untrusted-data deserialization vulnerability affecting Apache Roller versions 4.0.0 through 6.1.4. The XML-RPC endpoint accepts vendor extension types and deserializes attacker-controlled data before authenticating the requester or checking whether XML-RPC is disabled, allowing unauthenticated remote code execution. It is the same underlying vulnerability as CVE-2026-82384, which previously identified only version 6.1.5 as affected. The vulnerability is actively exploited and has a CVSS v3.1 score of 9.8.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution in the Roller JVM or servlet-container service context, potentially exposing application-accessible data, enabling unauthorized modification of application content and configuration, and disrupting service availability. The extent of host compromise depends on the permissions and resources available to the application service account.

Mitigation

If you can’t patch tonight, do this now.

If an immediate upgrade is not possible, set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, then restart Roller. Either configuration workaround addresses the vulnerable processing path. Disabling XML-RPC solely through the administration interface is insufficient because older releases deserialize requests before checking that setting.

Remediation

Patch, then assume compromise.

Upgrade to Apache Roller 6.1.6 or later. These releases disable XML-RPC vendor extension types and reject XML-RPC requests when the feature is disabled.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
APACHE-CVE-2026-129448Static analysis of 21 supplied files identifies a standalone exploitation and detection toolkit, not a Metasploit or Nuclei module. Its 14 executable/build-code files comprise three Python clients, five Bash scripts, four Java sources, and two Dockerfiles; XML and YAML provide deployment configuration. exploit/roller_exploit.py generates configurable ysoserial payloads and posts them as text/xml, with arbitrary-command, reverse-shell, alternate-gadget, timeout, and optional TLS-verification bypass support. poc/probe.py combines non-command-executing detection with an execution mode. scanner/roller_scan.py performs threaded detection from command-line targets, files, or stdin, supports proxies, and exports evidence as CSV or JSON lines. The central primitive is Base64 Java serialization inside the XML-RPC ex:serializable extension. With extensions enabled, request parsing can reach ObjectInputStream.readObject() before handler lookup or application authentication. Detection sends lab.ProbeGhost and looks for a class-loading fault; this establishes sink reachability, not successful command execution. Generic rejection substrings used for PATCHED classification can misclassify unrelated errors. The execution clients default to CommonsBeanutils1 and do not validate success independently; shell metacharacters are not interpreted by the documented Runtime.exec(String) command path. lab/setup.sh downloads dependencies and ysoserial, compiles Java helpers, and assembles minimal vulnerable/patched XML-RPC servlet applications. These are not complete Apache Roller installations. Docker Compose exposes them on ports 8080 and 8181; only the vulnerable service explicitly relaxes the documented TemplatesImpl setting. The patched lab demonstrates enabledForExtensions=false but does not implement the full Roller filter change described in the documentation. tests/smoke_test.sh checks Python syntax and detection responses, not end-to-end RCE. docs/ contains root-cause discussion and external references. The repository attributes the issue to CVE-2026-129448 and CVE-2026-82384, claims Roller 4.0.0–6.1.5 is affected and 6.1.6 onward fixed, and makes assertions about active exploitation and JDK defenses. These claims and exact runtime restrictions were not independently verified from the supplied files. Destructive-looking cleanup commands are confined to ordinary lab build/container cleanup and do not establish a fake exploit. No fixed attacker-controlled exfiltration destination is embedded in executable logic. Repository URL, git reference, and archive size were not provided; empty metadata and size 0 indicate unavailable information.Yanixos · Disclosed Nov 18, 2026 · python · bash · web · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationRollerapplication
FAQ

Frequently asked questions

Is CVE-2026-129448 exploited in the wild?
Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-129448?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-129448, the earliest disclosed Nov 18, 2026.
Is there a patch for CVE-2026-129448?
Upgrade to Apache Roller 6.1.6 or later. These releases disable XML-RPC vendor extension types and reject XML-RPC requests when the feature is disabled.
What products are affected by CVE-2026-129448?
Apache Software Foundation Roller.
How severe is CVE-2026-129448?
CVE-2026-129448 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.6% (77th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

47 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
scworldNews · Nov 18, 2026Apache releases security update for critical roller flaw | brief | SC MediaA critical untrusted-data deserialization vulnerability in Apache Roller's XML-RPC endpoint allows unauthenticated remote code execution. The content reports active exploitation. Apache recommends upgrading to version 6.1.6 or later. Administrators unable to upgrade can modify web.xml to disable extensions and remove the servlet mapping; disabling the feature through the administration interface alone is insufficient because deserialization occurs before settings are checked.Read more ↗security affairsNews · Nov 18, 2026Apache Roller RCE Flaw CVE-2026-129448 Under Active AttackA critical vulnerability (CVSS 9.8) in Apache Roller's XML-RPC endpoint permits unauthenticated remote code execution through unsafe deserialization before authentication. The article identifies it as the same vulnerability previously tracked as CVE-2026-82384, expanding the previously reported affected version 6.1.5 to include versions 4.0.0 through 6.1.4. Exploitation in the wild is confirmed, but attackers, victims, and attack details are undisclosed. Apache Roller 6.1.6 or later fixes the issue. Temporary workarounds are setting enabledForExtensions to false in WEB-INF/web.xml or removing the /roller-services/xmlrpc servlet mapping, followed by a restart. Disabling XML-RPC through the administration interface alone is insufficient.Read more ↗sh3llc0d3 blogNews · Nov 18, 2026Apache Roller Unauthenticated XML-RPC | ShellcodeA critical pre-authentication Java deserialization vulnerability affecting Apache Roller 4.0.0 through 6.1.4. Crafted XML-RPC vendor-extension payloads sent to /roller-services/xmlrpc can execute arbitrary code within the JVM/servlet container. Disabling XML-RPC through the administrative interface does not remove the vulnerable route. The content reports active exploitation and identifies Roller 6.1.6 or later as patched. Workarounds include disabling extension types, removing the XML-RPC servlet mapping, and restarting the application server.Read more ↗the hacker newsNews · Nov 18, 2026Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication RequiredA critical unauthenticated deserialization vulnerability in Apache Roller's XML-RPC endpoint allows remote code execution and is actively exploited. The endpoint deserializes vendor extension types before authenticating requests. Rated CVSS 9.8, CVE-2026-129448 covers versions 4.0.0–6.1.4 and is explicitly identified as the same vulnerability as CVE-2026-82384, which listed version 6.1.5 as affected. Upgrade to version 6.1.6 or later. Alternatively, set enabledForExtensions to false in WEB-INF/web.xml or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. Disabling XML-RPC through the administration UI alone is insufficient.Read more ↗
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity36Community discussion across Reddit, Mastodon, and other social sources.