Skip to content
securitytabs

Updated

Apache Roller blogging software flaw exploited to run code on servers

A critical flaw in Apache Roller, an open-source blogging platform, lets an attacker take over a server without logging in, and the Apache Software Foundation says it is being exploited. Anyone running Roller should move to the fixed release now.

Apache Roller remote code execution flaw exploited
Apache Roller remote code execution flaw exploited

What's new

TimelineWhat should my organization do?

Vulnerabilities

What happened

The Apache Software Foundation (ASF) released security updates for Apache Roller, a Java-based open-source blogging platform, to fix CVE-2026-129448. The flaw is unsafe handling of untrusted data (deserialization) in the platform's XML-RPC endpoint, and it can lead to remote code execution without authentication. [1][2][3]

NVD rates the flaw 9.8 on the CVSS scale. The CVE record describes it as affecting Roller releases before 6.1.5. [2]

Exploitation

According to the ASF, the flaw is under active exploitation in the wild. BleepingComputer reports that attackers are using it to gain code execution on vulnerable servers. The flaw is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue, its list of flaws attackers are using. The sources reviewed do not say who is behind the attacks or how many servers are affected. [2][1]

Timeline

  1. The Apache Software Foundation said the flaw was being exploited in the wild. [2]

  2. The Apache Software Foundation described the flaw as unauthenticated deserialization in the XML-RPC endpoint. [2]

  3. The Apache Software Foundation released Roller security updates. [1]

Explained

The technology and terms in this story. Learn more

Business ActionWhat this means inside your organization, and what to do about it, by company size.

Small business

No dedicated security staff; relies on providers

What to know

Only organizations that host their own Roller blog are directly affected; others depend on whoever runs the platform for them. [2]

What to do

  1. Ask your IT or hosting provider whether any Apache Roller site is in use. [2]
  2. If one is, ask that it be updated to release 6.1.5 or later. [2]

Mid-size company

A small IT or security team

What to know

The flaw needs no login and is reported as exploited, so exposed Roller servers may already be compromised. [2][1]

What to do

  1. Find Roller installations and update them to the release the Apache advisory names as fixed. [2][1]
  2. Check server logs for unexpected requests to the XML-RPC endpoint. [2]

Large enterprise

A security operations team

What to know

The ASF reports active exploitation of an unauthenticated code execution flaw in Roller; no indicators have been published in the cited coverage. [2][3]

What to do

  1. Inventory Roller instances, including internal blogs, and patch them to the fixed release. [1]
  2. Hunt for abnormal activity on Roller hosts, starting with requests to the XML-RPC endpoint. [2]

Sources

  1. [1]BleepingComputer · Nov 18, 10:35 UTC
    Apache warns of Roller RCE vulnerability exploited in attackscontext
  2. [2]The Hacker News · Nov 18, 17:10 UTC
    Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Requiredcontext
  3. [3]Security Affairs · Nov 18, 20:11 UTC
    Apache Roller RCE Flaw CVE-2026-129448 Under Active Attackcontext