HomeTech NewsCybersecurityApache Roller CVE-2026-129448 Is Being Actively Exploited

Apache Roller CVE-2026-129448 Is Being Actively Exploited

Apache has warned that CVE-2026-129448, a critical unauthenticated remote-code-execution flaw in its Roller weblog server, is being actively exploited. The project published the advisory on 17 November 2026. The same text was sent to the oss-security list at 11:02:58 GMT by Arnout Engelen of the Apache Software Foundation, and entered ENISA’s vulnerability catalogue as EUVD-2026-126955 at 11:03 the same day.

Roller is an open-source Java blogging server. The advisory, rated CVSS 3.1 9.8, says the bug affects versions 4.0.0 through 6.1.4. “Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code,” Apache wrote. “The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester.”

Apache has not said who is exploiting the flaw, how many servers have been hit, or how the attacks were spotted. The CVE is also absent from CISA’s Known Exploited Vulnerabilities catalog. Catalog version 2026.11.17, released at 17:53:15 GMT on 17 November and rechecked on 18 November, lists neither CVE-2026-129448 nor the earlier related identifier, CVE-2026-82384. The only addition in that release was Perforce’s Puppet Enterprise flaw, CVE-2026-115731, which TSN covered when CISA added it to the KEV list.

In brief

  • Apache says CVE-2026-129448, an unauthenticated code-execution flaw in Roller 4.0.0 through 6.1.4, is being actively exploited. It is the same bug as CVE-2026-82384, which had listed only 6.1.5.
  • The fix is Apache Roller 6.1.6 or later. Disabling XML-RPC in the administration UI is not enough; interim steps go to the server’s web.xml file or the XML-RPC servlet mapping, then a restart.
  • Apache has given no details of the attacks, and neither CVE is on CISA’s KEV list.

CVE-2026-129448 is the same bug as CVE-2026-82384, with a wider range

Apache’s November advisory is explicit about the relationship: “This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected.”

CVE-2026-82384 was published on 28 September 2026. The project’s security page already records it as a critical XML-RPC deserialization flaw, with a fix in 6.1.6. That earlier text described the same pattern — vendor extension types being deserialized during request parsing, before authentication — but only for version 6.1.5, and it did not say the issue was being actively exploited. It also noted that the servlet is mapped unconditionally, so parsing still happens when the global XML-RPC feature has been turned off.

The new identifier covers the older line: 4.0.0 through 6.1.4. The recommended upgrade for both records is 6.1.6 or later, which, Apache says, “disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.” Both advisories point to the same patch, Apache Roller pull request 171.

Apache credits n0mi1k as the finder of the issue. Matt Raible is credited as the reporter on the 17 November CVE; the September record named only n0mi1k.

The 6.1.6 upgrade is the fix; the admin toggle is not enough

Operators should move to Apache Roller 6.1.6 or later. For those who cannot upgrade immediately, Apache’s interim advice is to set enabledForExtensions to false in WEB-INF/web.xml, or to remove the /roller-services/xmlrpc servlet mapping, and then restart Roller.

The advisory is blunt about a setting that will look, on the screen, like a disable: “Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.” That is why the temporary steps are a configuration-file or servlet-mapping change and a restart, rather than a tick in the admin console.

The same week’s Java patching pile already includes OpenJDK and Red Hat’s advice on the Java4Shell flaw, a separate bug. Another recent Apache Software Foundation patch, HTTP Server 2.4.71, fixed a critical HTTP/2 remote-code-execution issue. Neither is this Roller XML-RPC flaw, but both are the sort of unauthenticated, internet-facing code-execution bugs that reward a prompt upgrade.

A second CVE can still be the first useful warning

CVE-2026-82384 already told anyone running Roller 6.1.5 to move to 6.1.6, in September. The November CVE does two further things. It says the same bug was present all the way back to 4.0.0, and it says the issue is now being exploited. A version range that named only 6.1.5 would have left operators on 6.1.4 and earlier looking as if they were out of scope. Those who moved from 6.1.5 to 6.1.6 when the first advisory appeared are already on the patched release. Those who stayed put because the September record did not list their version have now been told they were in range all along.

The administration-UI caveat is the practical sting of the same design. A toggle that appears to switch XML-RPC off can still leave the parser running on an unauthenticated request, which is why Apache’s interim steps go to web.xml or the servlet mapping. The official wording leaves little room for a “we turned it off in the console” workaround.

The absence of a KEV listing is not a reason to wait. CISA’s catalog is a federal owed-patch list, updated on its own timetable. The 17 November release added a Puppet Enterprise bug and did not add this one. Apache’s “actively exploited” sentence is already an official vendor statement. That gap may close later; the upgrade advice stays the same.

What Apache has still not published is any account of the attacks themselves. Without a victim count, a method write-up or a named campaign, readers should not infer the scale of what is happening in the wild — only that the vendor has now said exploitation is under way, and that the older version range is in play.

The next facts to watch are whether CISA adds CVE-2026-129448 or CVE-2026-82384 to the KEV list, and whether the Roller security page is updated to list the new identifier alongside the September record.

Sources

Related stories

The closest recent TSN account of a Java remote-code-execution advisory is this week’s Java4Shell post. The Puppet KEV addition is the contrast for a CISA listing this Roller flaw still lacks.

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.