Incident sheet · /security

Filed
Read
3 min · 694 words
Severity
Routine

Apache patches CVE-2026-129448 after active Roller exploitation

Apache has patched CVE-2026-129448 after active exploitation of Roller. Operators should move to 6.1.6, disable extensions and review XML-RPC exposure.

Apache warns of Roller RCE vulnerability exploited in attacks
FeedApache warns of Roller RCE vulnerability exploited in attacks — stevepb / pixabay

Event log

  1. CVE-2026-129448 affects Roller 4.0.0 through 6.1.4 and permits unauthenticated remote code execution.
  2. Apache Roller 6.1.6 disables vulnerable extension types and blocks malicious XML-RPC requests after the feature is turned off.
  3. The flaw is the same as CVE-2026-82384, whose earlier listing named only Roller 6.1.5.
  4. CISA ordered federal agencies to remediate the 13-year-old ActiveMQ flaw CVE-2026-34197 within two weeks in April.
  5. Since November 2021, CISA has cataloged 41 exploited Apache flaws; eight were also used by ransomware gangs.

Tom Whitfield

Apache has patched CVE-2026-129448, a critical Apache Roller flaw that threat actors are exploiting for remote code execution on vulnerable servers.

Apache Roller 6.1.6 disables the vulnerable vendor extension types and rejects malicious XML-RPC requests once the XML-RPC feature is switched off. Operators should treat the release as urgent, not housekeeping.

What is exposed?

Apache Roller is an open-source, Java-based group-blogging server with a much smaller market share than modern content management systems and blogging platforms.

That niche status offers little comfort. Apache has flagged the flaw as actively exploited in the wild, although it has not disclosed who is responsible or how many servers have been compromised.

Apache said in a Tuesday security advisory: "Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code."

The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. The request therefore reaches deserialization before Roller establishes who sent it, a rather important sequencing decision.

Apache also stated: "This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited."

The earlier listing did not reflect the full range of affected versions, according to the advisory. Current tracking therefore covers Roller 4.0.0 through 6.1.4, and the mitigation path points to 6.1.6 or later.

How should administrators respond?\n

Operators should upgrade to Apache Roller 6.1.6 or later immediately. The release disables extension types and rejects malicious XML-RPC requests after administrators turn off the XML-RPC feature.

Where an immediate upgrade is impossible, Apache recommends three temporary steps:

  • Set "enabledForExtensions" to "false" in WEB-INF/web.xml.
  • Remove the "/roller-services/xmlrpc" servlet mapping.
  • Restart Roller.

The setting and mapping changes mitigate the flaw while the upgrade remains pending. The administration interface alone does not provide equivalent protection.

Apache says disabling XML-RPC in the administration user interface is insufficient because older versions deserialize the request before checking whether that setting has been toggled on. In other words, the visible off switch arrives after the dangerous work.

What does this change for Roller administrators?

The immediate change is specific: deploy 6.1.6 or later, turn off XML-RPC and verify that vulnerable extension types remain disabled. Patching without checking those controls leaves a familiar administrative gap, which is hardly a useful form of reassurance.

The update also changes the incident response. This is no longer a vulnerability awaiting proof of exploitation; Apache has confirmed active attacks, while withholding the attacker identity and compromise count. Exposed, unpatched installations should be treated as suspect until upgraded and investigated.

The disclosure provides no scale. No attacker identity or server count appears in the advisory. For organizations that cannot establish whether an internet-facing Roller server was touched, one distinction matters: patched is a configuration state, while clean is an investigation finding.

Is this part of a wider Apache problem?

Apache has drawn repeated scrutiny. In April, the US Cybersecurity and Infrastructure Security Agency flagged a 13-year-old ActiveMQ vulnerability, CVE-2026-34197, as exploited and ordered federal agencies to secure their systems within two weeks.

Earlier this month, Apache also fixed a critical vulnerability in the HTTP/2 module of Apache HTTP Server. An unauthenticated attacker could use that flaw to gain remote code execution on unpatched servers.

The cumulative count is heavier. Since November 2021, CISA has added 41 Apache flaws to its catalog of vulnerabilities exploited in the wild. Eight were also abused by ransomware gangs.

Three recent items, spanning Roller, ActiveMQ and the HTTP server, now form an uncomfortable family portrait. Apache's remediation work is moving, but exposed organizations still carry both technical debt and operational delay.

The practical takeaway is direct: inventory internet-facing Apache deployments, apply current vendor fixes, and do not treat a disabled service label as proof that requests stop at the door. The Roller advisory shows why administrative controls must follow the order in which software processes a request.

via bleepingcomputer.com (Source)

Filed under

  • apache-roller
  • cve-129448
  • remote-code-execution
  • xml-rpc
  • active-exploitation
Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.

195 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›

Apache Roller CVE-2026-129448: Actively Exploited — CIO Monitor