← All updates

Security / News explained

Roller’s XML-RPC fix covers older releases too

The expanded Apache Roller advisory reaches releases before 6.1.5. The correction also explains why disabling a feature in the administration screen was insufficient.

By Zyel · Published · 4 min read

Apache’s November 17, 2026 record for CVE-2026-129448 extends the documented reach of an XML-RPC deserialization flaw to Roller 4.0.0 through 6.1.4. Apache identifies it as the same underlying vulnerability previously tracked for Roller 6.1.5 under CVE-2026-82384. The recommended correction is Roller 6.1.6 or later. [1] [2]

CISA added the CVE on November 20. Its entry lists November 23 for remediation and requests forensic triage. [3]

The practical change is the inventory question. A team that previously searched only for the version named in the original advisory should revisit older installations. In our reading, the expanded record closes a dangerous reasoning shortcut: an older release’s absence from the first affected-version statement did not establish that it was protected.

The request is parsed before the permission check

The original Apache record describes vendor extension types being deserialized while XML-RPC requests are parsed, before authentication. It also says the servlet remained mapped when the global XML-RPC feature was disabled. That combination allowed the affected parsing path without a special non-default configuration. [2]

Consider a hypothetical site that switched off XML-RPC in its administration screen years ago. An operator might reasonably expect the old publishing endpoint to be dormant. But a setting checked after request parsing cannot prevent an unsafe operation that has already happened. A settings screen cannot turn back the parsing clock.

Apache documents temporary server-level options for operators unable to upgrade immediately: disable extension types in WEB-INF/web.xml or remove the XML-RPC servlet mapping, then restart Roller. The expanded record specifically warns that disabling XML-RPC through the administration interface alone is insufficient. [1]

Those options illustrate the boundary that matters. A feature preference and an entry point’s actual behaviour are different pieces of evidence. Our recommendation is to record which supported correction or documented restriction is in effect, rather than accepting a screenshot of an unchecked box as the whole maintenance result.

Two identifiers describe one underlying problem

The September record names 6.1.5; the November record adds 4.0.0 through 6.1.4. Both point to the same correction. These identifiers should therefore be connected during review instead of becoming two unrelated tickets that leave an older installation outside either team’s scope. [1] [2]

The fix itself is dated context. Apache lists Roller 6.1.6 as released on September 24, 2026, and 6.1.7 on November 11. Its security policy says fixes ship on the current release line rather than being applied to older releases in place. [4]

The project’s download page currently recommends 6.1.7 and directs operators to its release notes and distribution-integrity checks. That establishes an available upstream release. It does not establish which package or application archive is serving a particular organisation’s website. [5]

The 6.1.7 notes also describe changes to AtomPub request handling, template wrappers and other application behaviour. Those details give an upgrade review something concrete to examine. Security maintenance and compatibility review can share a change window without treating either as a substitute for the other. [6]

A useful result identifies the running application

Imagine a hypothetical deployment with two application nodes behind one address. Replacing the archive on one node would leave an incomplete result if the second continued accepting requests with the older parser. This is an illustration of deployment verification, not a report of an incident or an assessment of any reader’s installation.

A useful handoff connects the affected release, the chosen correction, the deployed archive and the processes now serving requests. It also records any temporary restriction that still needs to be removed or replaced. That gives the next operator an answer more useful than “the upgrade was started.”

Where exposure or suspicious activity warrants investigation, preserve the relevant application and access evidence through the organisation’s response process. Updating the application closes a software path going forward; that maintenance action alone does not determine whether an earlier request reached it or what happened afterward.

The November development therefore deserves a fresh look at old installations, while keeping the dates straight. The software correction predates this week’s expanded coverage and exploitation listing. The immediate engineering value is to match the right versions to the existing fix and verify the running result.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. Apache CNA: expanded Roller XML-RPC vulnerabilityApache Software Foundation · Checked Nov 21, 2026
  2. Apache CNA: original Roller 6.1.5 advisoryApache Software Foundation · Checked Nov 21, 2026
  3. CISA Known Exploited Vulnerabilities catalogCISA · Checked Nov 21, 2026
  4. Roller security advisories and release datesApache Software Foundation · Checked Nov 21, 2026
  5. Current Apache Roller downloadsApache Software Foundation · Checked Nov 21, 2026
  6. Roller 6.1.7 changesApache Software Foundation · Checked Nov 21, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.