CVE Index中文
L4 · Septic Tank BlewApache · RCE · XML-RPCapache-roller-xmlrpc-rce

Apache expands exploited Roller XML-RPC RCE warning to older releases

Apache confirms active exploitation of Roller's XML-RPC deserialization flaw and expands affected versions to 4.0.0–6.1.4, alongside previously disclosed 6.1.5. Upgrade to 6.1.6 or later; 6.1.7 is current. Turning XML-RPC off in the old administration UI does not close the attack path.

Disclosed
Nov 17, 2026
Public disclosure date
Severity
CVSS 9.8 × 2
2 CVEs tracked here
Splash zone
Network-reachable Apache Roller 4.0.0–6.1.5 XML-RPC endpoints; no login or non-default XML-RPC setting is required.
java
In the wild
Yes
Apache reports active exploitation; the CVE's CISA ADP enrichment still says none.

What happened

The November 17 warning newly covers Roller 4.0.0–6.1.4 and reports active exploitation. Apache explicitly links it to the same XML-RPC vulnerability publicly disclosed for 6.1.5 on September 25. These identifiers describe one issue, not two independent attack paths or two victim totals. The original flaw and the 6.1.6 patch are not new in November.

A reachable XML-RPC endpoint can parse vendor extension types before checking credentials or whether XML-RPC is enabled. An unauthenticated attacker can therefore reach unsafe deserialization without changing the default configuration. The patched endpoint rejects disabled-service requests before parsing and refuses extension types even when XML-RPC is enabled. Updating the JVM alone is not the Roller application fix.

Apache’s direct exploitation warning supports the severity rating. Its CVE record also contains a CISA ADP SSVC assessment marked as no exploitation, unlike the CNA description. The CISA KEV feed checked on November 18 contains neither identifier; absence from KEV does not negate Apache’s report. The cited originals provide no campaign attribution, compromise count, start date or attacker indicators.

What’s in the bowl

XML-RPC deserialization in Roller 4.0.0–6.1.4

Vendor extension types are deserialized before authentication, allowing remote code execution; this expands the affected range of the already disclosed flaw.

Same XML-RPC flaw previously listed for Roller 6.1.5

Request parsing accepts attacker-controlled serialized bytes even when the global XML-RPC feature is disabled.

Fixed versions

ProductSafe fromNote
Apache Roller 4.0.0–6.1.56.1.6Minimum fix; current recommended release is 6.1.7

Crime-scene timeline

  1. Sep 5, 2026

    Apache merges the endpoint fix

    Pull request 171 disables unused extension types and gates the endpoint on the XML-RPC setting before parsing.

  2. Sep 24, 2026

    Roller 6.1.6 released

    This is the fixed release for the XML-RPC endpoint flaw.

  3. Sep 25, 20:12 UTC

    Apache publicly discloses the flaw for 6.1.5

    The original CVE-2026-82384 mailing-list notice predates its September 28 CVE-record publication.

  4. Nov 11, 2026

    Roller 6.1.7 released

    The current recommended release fixes other vulnerabilities too; it does not introduce a new minimum fix for this endpoint issue.

  5. Nov 17, 11:02 UTC

    Apache expands scope and confirms exploitation

    CVE-2026-129448 covers 4.0.0–6.1.4 and identifies the same flaw as CVE-2026-82384. Apache does not give an attack start date, attacker identity or victim count.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.