Apache warns of actively exploited remote-code flaw in Roller blogging software
A critical, no-login-required vulnerability in the open-source Apache Roller platform, first disclosed in September under a different identifier, has been reassigned a new CVE this week after the Apache Software Foundation confirmed it is being used in live attacks.

The Apache Software Foundation said this week that a critical, unauthenticated vulnerability in Apache Roller — open-source blogging and content-management software used for self-hosted sites, corporate intranets and institutional blogs — is being actively exploited and should be patched without delay. BleepingComputer first reported the advisory on Tuesday.
The flaw, now tracked as CVE-2026-129448, lets an attacker with no credentials send a single crafted request to the software's XML-RPC endpoint and execute arbitrary code on the underlying server. Apache disclosed a closely related version of the same bug in September under a different identifier, but this week's advisory both widens the list of affected releases and states for the first time that the flaw is being used in real attacks.
A wider blast radius, a higher-urgency warning
According to the advisory posted to Apache's security mailing list, the vulnerability carries a maximum-severity rating of 9.8 out of 10 on the industry's standard scoring system, as recorded in the National Vulnerability Database, and affects Roller versions 4.0.0 through 6.1.4 — effectively every release of the software going back more than a decade. A related flaw in version 6.1.5, logged in September as CVE-2026-82384, is described by Apache as the same underlying vulnerability. The bug sits in Roller's XML-RPC servlet, which the advisory says accepts vendor extension types and deserializes them before authenticating the requester, letting an attacker smuggle in a malicious object that runs before any login check takes place.
Apache's own vulnerability tracker lists 21 separate Roller security advisories updated this month alone, most of them cross-site-scripting, request-forgery and data-exposure bugs folded into the newly released Roller 6.1.7, published November 11. That release also carries the fix for the deserialization flaw, which first shipped in version 6.1.6 in September by disabling the vulnerable "vendor extension" feature outright and rejecting XML-RPC requests once that feature is off.
An old bug with a newly confirmed blast radius
Roller is a Java-based, multi-user blogging platform that entered the Apache Incubator nearly two decades ago and has since been run by universities, government offices and corporate communications teams operating self-hosted blogs rather than commercial platforms. Because it ships as a downloadable server package rather than a hosted service, each installation is patched — or left unpatched — entirely at the discretion of whoever runs it, with no central registry of how many copies exist or where.
That makes it a recurring target once a flaw becomes public. Working exploit code for the original version of the bug appeared on GitHub within days of its September disclosure, and independent technical analysis published this week by the security-research firm Corgea found that triggering it requires nothing more than a single crafted HTTP request, with no authentication of any kind. As of Tuesday evening, neither CVE had been added to the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog, which means federal civilian agencies are not yet under a binding patch deadline for it, even though Apache itself says exploitation is already under way.
Who is exposed, and what Apache isn't saying
Anyone running a Roller instance reachable from the open internet on a version earlier than 6.1.6 is exposed, with no login or user interaction required for an attacker to gain a foothold. Apache's advisory does not say how many servers have been compromised or identify who is behind the activity, and the foundation has not released indicators of compromise such as attacker infrastructure or malware samples. Disabling XML-RPC through Roller's own administrative settings does not stop the attack on affected versions, the advisory notes, because the vulnerable code path processes incoming requests and deserializes their contents before the software checks whether that feature has been switched off.
"This issue is being actively exploited."
That line, from Apache's advisory, is the crux of why security teams are treating this as more urgent than the September disclosure: a previously theoretical, unauthenticated code-execution bug has moved into confirmed, live use against real servers, in a piece of widely distributed open-source software with no single owner tracking who still runs it.
What comes next
Apache's guidance is direct: upgrade to Roller 6.1.7. For administrators who cannot upgrade immediately, the foundation recommends setting the "enabledForExtensions" option to false in the application's web.xml configuration file or removing the XML-RPC servlet mapping entirely, then restarting the server — and blocking requests to the vulnerable endpoint at a firewall or reverse proxy in the meantime. Security researchers reviewing the advisory have gone further, suggesting that any internet-exposed Roller server on an affected version should be treated as potentially already compromised until an administrator has checked its logs, given how long a working exploit has been publicly available.
Whether the vulnerability is added to CISA's exploited-vulnerabilities catalog in the coming days, which would set a formal remediation deadline for U.S. federal systems, is likely to be the next official signal of how widely the bug is being used. For now, the burden of tracking exposure falls on individual Roller operators, in keeping with how self-hosted open-source software is maintained: there is no vendor support contract to call, and no central count of which servers have already been patched.
BleepingComputer — Apache warns of Roller RCE vulnerability exploited in attacks
Apache Software Foundation — Apache Roller security advisories
Apache Software Foundation — Security advisory mailing-list thread, CVE-2026-129448
Corgea Research — CVE-2026-129448/82384: Apache Roller XML-RPC deserialization exploited

Google Says Attackers Built an AI Tool That Turns Patches Into Exploits With No Human Involved

Google quietly triples how long it keeps "deleted" Gemini chats
