CVE-2026-129448 — a critical deserialization flaw in Apache Roller — is being actively exploited in the wild, Apache warned in a security advisory this week.
CVE-2026-129448: Apache’s advisory and what’s known
Apache released security updates after flagging a vulnerability in Apache Roller that "allows an unauthenticated remote attacker to execute arbitrary code." The project said the flaw affects Apache Roller versions 4.0.0 through 6.1.4 and that the issue is "being actively exploited." Apache also said it has not yet published details about the ongoing attacks, including who is responsible or how many servers have been compromised.
How the vulnerability works: XML-RPC deserialization
Apache attributes the risk to the XML-RPC endpoint accepting vendor extension types and deserializing them before authenticating the requester. In its advisory Apache spelled out the core problem: "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."
Apache also noted this is the same underlying issue that earlier appeared under CVE-2026-82384, which had been reported as affecting only Roller 6.1.5. The current advisory expands the affected-version range and confirms active exploitation.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scramblePatch and temporary mitigations for Roller administrators
Apache’s direct guidance is immediate: upgrade to Apache Roller 6.1.6 or later. The 6.1.6 release disables the extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature.
For administrators who cannot immediately upgrade, Apache lists a short set of temporary mitigations you can apply now: set "enabledForExtensions" to "false" in WEB-INF/web.xml; remove the "/roller-services/xmlrpc" servlet mapping; and restart Roller. Apache warned that disabling XML-RPC via the administration user interface is not sufficient on older Roller releases because those versions deserialize requests before checking the UI setting.
CISA’s recent actions and the wider Apache advisory context
The Roller advisory arrives against a backdrop of other Apache vulnerabilities flagged as exploited. In April, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) flagged a 13‑year‑old Apache ActiveMQ vulnerability (CVE-2026-34197) as exploited in attacks and required federal agencies to secure affected systems within two weeks. Earlier this month Apache also fixed a critical vulnerability in the HTTP/2 module of Apache HTTP Server that could be exploited for remote code execution on unpatched servers.
Since November 2021, CISA has added 41 Apache flaws to its catalog of vulnerabilities exploited in the wild; eight of those were also abused by ransomware gangs, according to the same record-keeping Apache referenced.
What this means for Roller users, CISA/regulators, and IT/security teams
- Roller users and administrators: Immediately prioritize the upgrade to Apache Roller 6.1.6 or later. If an immediate upgrade is impossible, apply the WEB-INF/web.xml and servlet-mapping mitigations and restart Roller, and do not rely on the administration UI toggle alone for protection on older releases.
- CISA and regulators: The active exploitation designation strengthens the case for rapid assessment and mitigation in environments that run Apache Roller; the agency’s prior directives on Apache flaws signal the scale at which federal and regulated entities are expected to act.
- IT and security teams at affected organizations: Treat this as a live code-execution risk tied to XML-RPC deserialization; inventory Roller deployments, apply the patch or the manual mitigations, and monitor systems for signs of compromise, keeping in mind Apache has not published the attack details or the scope of incidents.
The record here is stark and specific: a deserialization weakness in an XML-RPC endpoint, tracked as CVE-2026-129448, is being weaponized against unpatched Roller instances. Apache’s fix and the manual mitigations it outlines are narrow and actionable; what remains unanswered is how widespread the exploitation already is and who is carrying it out. For now the clear next step is technical and immediate — apply Roller 6.1.6 or execute the recommended configuration changes and restart — and then watch for further advisories from Apache and related guidance from CISA.




