Tuskira AdvisoryReported, not on KEVLast updatedNovember 17, 2026

CVE-2026-129448

How to tell if CVE-2026-129448 (Apache Roller XML-RPC code execution) is reachable in your environment

Latest change
First published. Apache extended the Roller XML-RPC flaw to 4.0.0 through 6.1.4 and says it is being exploited.

Reachable if you run Apache Roller 4.0.0 through 6.1.5 and its /roller-services/xmlrpc path can be reached over the network. No login is needed, and turning off XML-RPC in the admin UI does not close it

Affected
Apache Roller 4.0.0 through 6.1.5 (CVE-2026-129448 and CVE-2026-82384)
Exploitation
Apache says it is being actively exploited. Not on CISA KEV.
Fix
Upgrade to 6.1.6 or later. Apache lists 6.1.7 as the best available release.
Can't patch today
Set enabledForExtensions to false in WEB-INF/web.xml or remove the xmlrpc servlet mapping, then restart, per Apache

Apache says this flaw is being exploited, and every Apache Roller release from 4.0.0 through 6.1.5 has it. An attacker with no account can run code on the server by sending a request to Roller's XML-RPC endpoint. Turning off XML-RPC in Roller's admin settings does not close it, because older versions process the request before they check that setting.

Apache published CVE-2026-129448 on November 17 and rates it 9.8 Critical. It is the same bug as CVE-2026-82384, published September 25, which listed only version 6.1.5. The new CVE extends the affected range back to 4.0.0. Both are fixed in 6.1.6 or later. Apache's download page recommends 6.1.7, released November 11, which also fixes 15 other flaws.

Apache has not said who is exploiting it or how widely. It is not on CISA's Known Exploited Vulnerabilities catalog as of the November 13, 2026 catalog. A public repository targets the 6.1.5 issue, but its own notes say it ships no working payload and it does not claim testing on a real install. We read it and did not run it.

Is it reachable for you?

What it is. Apache says Roller's XML-RPC endpoint accepts vendor extension types and turns them back into Java objects before it checks who sent the request. That step can be abused to run code. Apache's September advisory adds that the endpoint is mapped unconditionally, so no special configuration is needed.

Who is most exposed. Any internet-facing Roller site on 6.1.5 or earlier. XML-RPC exists so desktop blog clients can post to Roller, which means the endpoint usually sits on the same public address as the blog itself.

Checks, in three tiers. The first decides exposure. The second and third decide priority. Run these only on systems your organization owns.

  1. Which Roller version runs? Check the version in the site footer, the about page or the release notes of the deployed build. Anything from 4.0.0 through 6.1.5 is affected.
  2. Can /roller-services/xmlrpc be reached? From outside your network, check whether the path answers at all. If a proxy or firewall already blocks it, exposure drops to internal users. If it answers, assume the flaw is reachable whatever the admin setting says.
  3. Is the workaround in place? Open WEB-INF/web.xml in the deployed application and check whether enabledForExtensions is set to false or the xmlrpc servlet mapping has been removed. A server where neither is true goes to the top of the list.
What Tuskira checks for this flaw in your environment
Apache Roller servers on 6.1.5 or earlier with /roller-services/xmlrpc reachable
Internal systems reachable from those Roller servers
Across every system you run.
See how Tuskira finds exposed systems

Compensating controls (test them, don't assume them)

Apache says to upgrade. For servers that can't be upgraded right away, Apache gives this workaround.

  • Turn off extension types. Set enabledForExtensions to false in WEB-INF/web.xml, then restart Roller, per Apache.
  • Or remove the endpoint. Remove the /roller-services/xmlrpc servlet mapping, then restart Roller, per Apache. Desktop blog clients that post through XML-RPC will stop working.
  • Don't rely on the admin setting. Apache says disabling XML-RPC in the administration UI is not enough on older versions.

What to look for in logs

Apache has published no indicators of compromise for this flaw. Until it does, upgrade to 6.1.6 or later, or apply Apache's web.xml workaround above.

FAQ

Am I exposed to CVE-2026-129448?

You are if you run Apache Roller 4.0.0 through 6.1.5 and its /roller-services/xmlrpc path can be reached. No login is needed.

Is it being exploited?

Apache says it is being actively exploited. Apache has not given details, and it is not on CISA KEV as of the November 13, 2026 catalog.

How is it related to CVE-2026-82384?

Apache says it is the same vulnerability. CVE-2026-82384 listed only 6.1.5. CVE-2026-129448 covers 4.0.0 through 6.1.4. Upgrading to 6.1.6 or later fixes both.

We turned off XML-RPC in the admin panel. Are we safe?

No. Apache says older versions process the request before they check that setting. Upgrade, or apply the web.xml workaround and restart.

Should we go to 6.1.6 or 6.1.7?

Either fixes this flaw. Apache's download page lists 6.1.7 as the best available release, and it fixes 15 more issues, so it is the better target.

Vendor
Apache Software Foundation
Product
Apache Roller, Java blog server
Affected versions
Apache Roller 4.0.0 through 6.1.4 (CVE-2026-129448) and 6.1.5 (CVE-2026-82384), per Apache. Every release from 4.0.0 through 6.1.5 is affected
Vulnerable component
XML-RPC endpoint at /roller-services/xmlrpc, used by desktop blog clients
CVSS
9.8 Critical (Apache, CVSS 3.1). NVD has not added its own score
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (Apache)
CWE
CWE-502 (Apache)
Exploitation
Reported, not on KEV
CISA KEV added
Patch
Apache Roller 6.1.6 or later fixes both CVEs. Apache's download page lists 6.1.7 (Nov 11, 2026) as the best available release, and it fixes 15 more flaws

Updates

Nov 17, 2026. First published. Apache published CVE-2026-129448, extending CVE-2026-82384 to Roller 4.0.0 through 6.1.4, and says it is being actively exploited; not on CISA KEV.

Sources

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.