Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Apache Roller XML-RPC Flaw Is Being Exploited, Project Warns

Apache says CVE-2026-129448 is actively exploited against Roller XML-RPC. Upgrade to 6.1.6 or later; disabling XML-RPC in the UI alone is insufficient.

Apache Roller XML-RPC Flaw Is Being Exploited, Project Warns
PUBLISHED

IPCRIME NEWSROOM | NOVEMBER 19, 2026

The Apache Software Foundation has warned of active exploitation of an unauthenticated code-execution vulnerability in Apache Roller, the Java blogging platform. The issue, CVE-2026-129448, was disclosed November 17 and is receiving renewed attention November 19 because earlier mitigation assumptions may leave older deployments exposed.

Unsafe XML-RPC deserialization before authentication

The Roller XML-RPC endpoint accepts certain extension types and deserializes input before authenticating the request. A crafted request can lead to code execution with the privileges of the affected application. Apache rates the flaw critical at CVSS 9.8 and confirms exploitation without publishing a list of victims or identifying an attacker.

Why an earlier fix created confusion

Apache’s advisory says CVE-2026-129448 describes the same underlying vulnerability as CVE-2026-82384, which originally addressed Roller 6.1.5. The broader disclosed affected range includes 4.0.0 through 6.1.4, and the project recommends version 6.1.6 or later to remove the unsafe behavior. Version 6.1.7 is also available and includes other security updates.

What will not protect older installations

The vendor specifically cautions that turning XML-RPC off in Roller’s administrative interface alone is insufficient in affected versions, because the request can be deserialized before the setting is checked. For teams unable to upgrade immediately, Apache describes disabling extension types in the server-side configuration or removing the XML-RPC servlet mapping and restarting the application. These are emergency mitigations to be tested against legitimate integrations.

Patch and look backward

Determine whether the application is internet-accessible and whether the XML-RPC endpoint is exposed. Use the vendor’s release path and verify the running build after restart. Preserve relevant server and application logs, review for unexpected deployments or changes, and treat evidence of earlier exploitation as a separate incident-response case. Avoid assuming that a successful patch reverses any malicious code already executed.

Source documentation

Reporting based on the documents linked above. The featured image is conceptual IPCRIME artwork, not a photograph of the described incident.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.