Skip to navigation

Threat reportVulnerabilityTL-2026-6329

Apache Roller unauthenticated RCE via XML-RPC deserialization (CVE-2026-129448 / CVE-2026-82384) exploited in attacks

criticalACTIVE

A critical CWE-502 flaw in Apache Roller's XML-RPC endpoint deserializes vendor extension types before authenticating the requester, letting unauthenticated remote attackers execute code. Apache/NVD state it is being actively exploited; fixed in Roller 6.1.6 or later. First disclosed .

Key facts

IdentifiersTL-2026-6329, CVE-2026-129448, CVE-2026-82384
SeverityCRITICAL
CVSS9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
First disclosed
Affected productsApache Software Foundation Apache Roller
Weaknesses (CWE)CWE-502
ToolsApache Commons Collections, ysoserial
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1190 Exploit Public-Facing Application, T1587.004 Exploits, T1588.005 Exploits, T1592.002 Software, T1595.002 Vulnerability Scanning
MotivationUNKNOWN
Target sectorstechnology, news - media, education, government administration
Target regionsGlobal
Detection rules9 (1 shown free)
Sources11 cited sources

Detection coverage

As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6329 across Splunk SPL, Microsoft KQL and Sigma, covering 11 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Apache Roller XML-RPC Endpoint POST from External Source (CVE-2026-82384 / CVE-2026-129448) — Exploitation

Detects unauthenticated POST requests from non-RFC1918 sources to the Apache Roller XML-RPC servlet (/roller-services/xmlrpc and the /roller/ context-path variant). Vulnerable Roller 4.0.0-6.1.5 deserializes ex:serializable vendor extension types during request parsing before authentication, so any external POST to this path is the exploit trigger (CWE-502, T1190) and also matches the public PoC check/bulk-scan modes (T1595.002). Apache states the flaw is actively exploited.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1595.002
  • Data sources: web:access_combined (index=web), Apache/Tomcat/reverse-proxy access logs, CommonSecurityLog (WAF/proxy)
  • Severity: critical
  • Confidence: high

Splunk SPL

index=web sourcetype=access_combined method=POST (uri_path="/roller-services/xmlrpc" OR uri_path="/roller/roller-services/xmlrpc") earliest=-24h
| eval is_internal=if(cidrmatch("10.0.0.0/8",clientip) OR cidrmatch("172.16.0.0/12",clientip) OR cidrmatch("192.168.0.0/16",clientip) OR cidrmatch("127.0.0.0/8",clientip),1,0)
| where is_internal=0
| stats count AS requests min(_time) AS first_seen max(_time) AS last_seen dc(host) AS roller_hosts_hit values(host) AS hosts values(status) AS statuses values(useragent) AS user_agents sum(bytes) AS bytes_total BY clientip
| eval first_seen=strftime(first_seen,"%F %T"), last_seen=strftime(last_seen,"%F %T")
| sort - requests

Microsoft KQL

CommonSecurityLog
| where TimeGenerated > ago(24h)
| where RequestMethod =~ "POST"
| where RequestURL has "/roller-services/xmlrpc"
| where not(ipv4_is_private(SourceIP))
| summarize Requests=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), Targets=make_set(DestinationIP, 20), Hosts=make_set(DestinationHostName, 20) by SourceIP, DeviceVendor, DeviceProduct
| order by Requests desc

Sigma

title: Apache Roller XML-RPC Endpoint POST (CVE-2026-82384 / CVE-2026-129448)
id: a3f1c2d4-6b7e-4c85-9d21-5e8f0a1b2c31
status: experimental
description: Detects POST requests to the Apache Roller XML-RPC servlet, the unauthenticated entry point for the CWE-502 deserialization RCE in Roller 4.0.0-6.1.5.
references:
    - https://nvd.nist.gov/vuln/detail/cve-2026-129448
    - https://www.openwall.com/lists/oss-security/2026/09/25/17
    - https://github.com/apache/roller/pull/171
author: Threadlinqs Team
date: 2026-11-18
tags:
    - attack.initial-access
    - attack.t1190
    - attack.reconnaissance
    - attack.t1595.002
    - cve.2026.82384
    - cve.2026.129448
logsource:
    category: webserver
detection:
    selection:
        cs-method: 'POST'
        cs-uri-stem|endswith: '/roller-services/xmlrpc'
    condition: selection
falsepositives:
    - Legitimate Blogger/MetaWeblog API clients (desktop blog editors, mobile apps) posting to a patched or intentionally exposed Roller instance
    - Authorized vulnerability scanners
level: high

Known false positives:

  • Legitimate XML-RPC (Blogger/MetaWeblog) clients such as desktop blog editors or mobile apps publishing to an intentionally exposed Roller
  • Authorized external vulnerability scanning of the Roller host

Tuning notes: Allowlist known publishing clients/IP ranges. If XML-RPC is not used, treat every external hit as malicious and block /roller-services/xmlrpc at the proxy/WAF. Adjust index/sourcetype and the clientip field to your proxy log format (X-Forwarded-For). Correlate hits with the child-process detections (TL-2026-6329-SPL-002) on the same host. Patched 6.1.6+ returns 404 when XML-RPC is disabled, so 200/500 responses indicate a vulnerable instance.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Java Serialized Object / ex:serializable in Roller XML-RPC Request Body (CVE-2026-82384) · unlock with TL Creds
  • Roller/Tomcat JVM Spawning Download or Interpreter Tooling (Ingress Tool Transfer) · unlock with TL Creds
  • Roller/Tomcat Java Process Outbound Connection to Public IP on Non-Standard Port · unlock with TL Creds
  • Apache Roller XML-RPC POST Returning Server Error (Failed Gadget / Probing Attempts) · unlock with TL Creds
  • Roller/Tomcat JVM Spawning cmd.exe or PowerShell on Windows · unlock with TL Creds
  • Reverse Shell Command Spawned by Roller/Tomcat JVM on Linux · unlock with TL Creds
  • Roller/Tomcat JVM Spawning Unix Shell (CVE-2026-82384 RCE Post-Exploitation) · unlock with TL Creds
  • Java Process DNS Lookup to OAST/Callback Domain (Deserialization Probe, CVE-2026-82384) · unlock with TL Creds

Indicators of compromise

As of 2026-11-18, Threadlinqs Intelligence tracks 11 indicators of compromise for TL-2026-6329.

Sample indicators (1 of 11)

  • URL: hxxps://github[.]com/murrez/CVE-2026-82384

Defanged, TLP:CLEAR. Full set of 11 indicators: unlock with TL Creds.

11 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Apache Roller is a Java blog server. Its XML-RPC servlet (mapped at /roller-services/xmlrpc) is configured to enable the XML-RPC library's vendor extension types. When a request is parsed, an extension element (the public PoC uses ex:serializable carrying a base64-encoded Java serialized object) is deserialized during request parsing, before any Blogger/MetaWeblog authentication check. An unauthenticated remote attacker can therefore make the server deserialize attacker-controlled bytes, which can lead to remote code execution in the Roller process. The servlet is mapped unconditionally, so parsing occurs even when the XML-RPC feature is disabled in the admin UI, and no non-default configuration is required.

Two CVE records describe the same underlying vulnerability. CVE-2026-82384 (published 2026-09-28 after oss-security disclosure on 2026-09-25, finder credited as n0mi1k, CVSS 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) listed only Roller 6.1.5 as affected. CVE-2026-129448 (NVD record published 2026-11-17) widens the affected range to Apache Roller 4.0.0 through 6.1.4 and states it is the same vulnerability as CVE-2026-82384 and that it is being actively exploited. Together the exposure spans 4.0.0 through 6.1.5. A CVSS score for CVE-2026-129448 itself was not stated in the sources reviewed; the 9.8 score is taken from the sibling record CVE-2026-82384. Apache has not disclosed attack details, the attackers, or the number of compromised servers. No in-the-wild IOCs or attribution have been published, and neither CVE was in CISA KEV when checked by third-party reporting.

A public proof-of-concept repository (github.com/murrez/CVE-2026-82384, MIT licensed) provides check, exploit and bulk-scan modes against POST /roller-services/xmlrpc (and a /roller/roller-services/xmlrpc variant). It ships no gadget chains; exploitation depends on the target classpath (Commons Collections is cited as a common example) and externally generated payloads (e.g. ysoserial). Version fingerprinting via the site footer/about page is suggested by the PoC.

The upstream fix (apache/roller PR #171, merged 2026-09-05) disables the extension types in WEB-INF/web.xml and adds an XmlRpcEnabledFilter that returns 404 when webservices.enableXmlRpc is off, rejecting requests before the body is read. Release 6.1.6 (2026-09-24) contains the fix; 6.1.7 (2026-11-11) fixes 15 further CVEs, including a separate XML-RPC client-side deserialization issue (CVE-2026-123374, affects 4.0-6.1.6, triggered by a malicious ping-target response) that should not be confused with this one.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter

Initial Access

T1190 Exploit Public-Facing Application

Resource Development

T1587.004 Exploits; T1588.005 Exploits

Reconnaissance

T1592.002 Software; T1595.002 Vulnerability Scanning

Remediation

Patches

  • Apache Roller 6.1.6 or later (fix disables extension types and rejects requests when XML-RPC is disabled)
  • Apache Roller 6.1.7 (2026-11-11) recommended; read release notes first as some changes affect existing sites

Immediate actions

  • Upgrade Apache Roller to 6.1.7 (6.1.6 is the minimum release containing the fix for this flaw)
  • If upgrading is not immediately possible, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller
  • Do not rely on disabling XML-RPC in the Roller admin UI: vulnerable versions deserialize the request before checking that setting
  • Hunt web/proxy logs for POST requests to /roller-services/xmlrpc and /roller/roller-services/xmlrpc, especially from untrusted sources, and treat internet-exposed unpatched instances as potentially compromised

Workarounds

  • Set enabledForExtensions=false in WEB-INF/web.xml and restart
  • Remove the /roller-services/xmlrpc servlet mapping and restart

Longer-term hardening

  • Restrict or block external access to /roller-services/xmlrpc at the reverse proxy or WAF if XML-RPC clients are not required
  • Run Roller under a least-privilege account with egress filtering to limit post-exploitation impact
  • Inventory Apache Roller instances and subscribe to Apache Roller security announcements

Affected and fixed versions

  • Apache Software Foundation — Apache Roller
    Vulnerable versions: 4.0.0 through 6.1.4 (CVE-2026-129448); 6.1.5 (CVE-2026-82384)
    Fixed in: 6.1.6 or later; 6.1.7 recommended

Timeline

  • apache/roller PR #171 merged: disables XML-RPC vendor extension types in web.xml and adds XmlRpcEnabledFilter gating the endpoint
  • Apache Roller 6.1.6 released with the fix for the unauthenticated XML-RPC deserialization flaw
  • CVE-2026-82384 disclosed on oss-security by David M. Johnson (Apache Roller); finder credited as n0mi1k; CVSS 3.1 9.8; affected listed as 6.1.5
  • CVE-2026-82384 record published to NVD; a public PoC repository (murrez/CVE-2026-82384) is subsequently referenced by aggregators
  • Apache Roller 6.1.7 released fixing 15 CVEs, including the separate client-side XML-RPC deserialization flaw CVE-2026-123374
  • NVD publishes CVE-2026-129448: same vulnerability, affected range widened to Roller 4.0.0 through 6.1.4, record states it is being actively exploited
  • BleepingComputer reports Apache's warning that the Roller RCE is exploited in attacks; no attacker, scale or IOC details disclosed

Sources cited

Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats