Apache Roller CVE-2026-129448: Act Now on an Actively Exploited RCE

Apache says CVE-2026-129448 is a critical, actively exploited pre-authentication remote-code-execution flaw affecting Roller 4.0.0 through 6.1.5. Upgrade to 6.1.6 or later.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Apache Roller CVE-2026-129448: Act Now on an Actively Exploited RCE

Reporting cutoff: November 17, 2026, 7:19 p.m. EST / 00:19 UTC.

Apache says CVE-2026-129448 is being actively exploited. The flaw lets an unauthenticated remote attacker execute arbitrary code through deserialization in Apache Roller’s XML-RPC endpoint. [1]

CRITICAL • ACTIVE EXPLOITATION

Bottom line

Apache identifies Roller 4.0.0 through 6.1.4 as affected and says the same vulnerability separately covered Roller 6.1.5. Upgrade to 6.1.6 or later. [1]

Apache’s download page currently calls Roller 6.1.7 the “best available” general-availability release. [2]

SeverityCVSS 3.1: 9.8 Critical [1]
Attack pathNetwork, low complexity, no privileges or user interaction [1]
FixRoller 6.1.6 or later [1]

Who should treat this as urgent?

Exposure predicate: an organization is in scope when it runs Apache Roller 4.0.0 through 6.1.5 and attacker-controlled network traffic can reach the affected XML-RPC endpoint. The record says deserialization occurs before requester authentication. [1]

The flaw is specific to Apache Roller; this advisory does not apply to WordPress, unrelated Apache projects, or Java servers merely because they use Java. [1]

What administrators should do

  1. Identify every Apache Roller deployment and its running version. Compare each installation with Apache’s affected range before acting. [1]
  2. Upgrade to Roller 6.1.6 or later; use 6.1.7 where compatible. Apache names 6.1.6 as the fixed floor and lists 6.1.7 as the best available GA release. [1][2]
  3. If an immediate upgrade is impossible, apply Apache’s exact temporary workaround. Set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. [1]
  4. Do not rely only on the administration UI’s XML-RPC toggle. Apache says older releases deserialize the request before checking that setting. [1]
  5. Verify the outcome. Confirm the running application reports Roller 6.1.6 or later; if using the temporary workaround, confirm the intended web.xml change is active after restart. [1]

What the public record does not tell us

The frozen Apache CNA record does not name an exploiting actor or a victim. [1]

CVE-2026-129448 was not listed in CISA’s Known Exploited Vulnerabilities catalog version 2026.11.17 available at this reporting cutoff. That catalog absence does not override Apache’s direct statement that exploitation is active. [1][3]

The IT Guys did not access customer systems or private telemetry, so local exposure is unknown.

Why the version wording needs care

The structured affected range in the new record is 4.0.0 up to, but not including, 6.1.5; the same record says CVE-2026-82384 listed 6.1.5 as affected. The practical combined range is therefore 4.0.0 through 6.1.5, with 6.1.6 or later as the fixed line. [1]

Sources

  1. Apache CNA record for CVE-2026-129448 — published and updated November 17, 2026; retrieved November 17, 2026, 7:19 PM EST.
  2. Apache Roller downloads — current GA download guidance; retrieved November 17, 2026, 7:19 PM EST.
  3. CISA Known Exploited Vulnerabilities catalog — catalog version 2026.11.17, released 2026-11-17T17:53:15.5664Z; retrieved November 17, 2026, 7:19 PM EST.