--- title: "Apache Roller CVE-2026-129448 Exploited: Upgrade to 6.1.6+" url: https://playciso.com/blog/apache-roller-cve-2026-129448-exploited updated: 2026-11-20 section: Blog publisher: PlayCISO --- # Apache Roller CVE-2026-129448 Exploited: Upgrade to 6.1.6+ > Apache says Roller CVE-2026-129448, an unauthenticated XML-RPC RCE in 4.0.0 to 6.1.4, is actively exploited. Admin toggle not enough; what to do. Source: https://playciso.com/blog/apache-roller-cve-2026-129448-exploited · Published: 2026-11-20 · Publisher: PlayCISO (https://playciso.com) Primary source: https://lists.apache.org/thread/q573hvzrjyjvb5z600z8hgk044jqfshc --- **Apache says attackers are exploiting CVE-2026-129448, an unauthenticated remote code execution flaw in the XML-RPC endpoint of the Apache Roller blog server.** In [its announcement of 17 November 2026](https://lists.apache.org/thread/q573hvzrjyjvb5z600z8hgk044jqfshc), Apache says Roller 4.0.0 through 6.1.4 deserializes data sent to the XML-RPC endpoint before it checks who sent it, and that "this issue is being actively exploited". The fix is **Roller 6.1.6 or later**. Apache also warns that **turning XML-RPC off in the administration interface does not protect older versions**, because they deserialize the request before they check that setting. **Who this is for:** CISOs, vulnerability-management leads and anyone responsible for Java web applications, especially old corporate or team blogs running on Tomcat. *Based on Apache's announcements, the CVE.org records, the Roller downloads page and the Apache release archive, read on 20 November 2026. PlayCISO is not affiliated with Apache. We publish no exploit details.* Confirmed vs not yet known **Apache confirms (announcement and CVE record, 17 Nov 2026):** Roller 4.0.0 through 6.1.4 are affected; the XML-RPC endpoint deserializes vendor extension types before authenticating; it is the same vulnerability as CVE-2026-82384 (which listed only 6.1.5); "This issue is being actively exploited"; upgrade to 6.1.6 or later; disabling XML-RPC in the administration UI "is not enough". Severity: critical, CVSS 3.1 9.8. Credit: n0mi1k (finder) and Matt Raible (reporter). **CISA:** CVE-2026-129448 was not in the [KEV catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) as of catalog version 2026.11.18. CISA's SSVC enrichment of the CVE record, dated 18 November, records "Exploitation: none", "Automatable: yes" and "Technical Impact: total". That entry does not reflect Apache's statement; expect it to be revised. **Not yet known:** who is exploiting it, against which sites, since when, and whether attackers used the earlier CVE-2026-82384 disclosure (25 September) to target older releases. Apache gives no detail beyond "actively exploited". Some security news sites have covered the announcement; we found no primary source with more. ## Affected and fixed versions | Roller version | CVE | Status | Action | | --- | --- | --- | --- | | 4.0.0 through 6.1.4 | CVE-2026-129448 | Affected; actively exploited per Apache | Upgrade to 6.1.6 or later | | 6.1.5 | CVE-2026-82384 | Affected (same flaw) | Upgrade to 6.1.6 or later | | 6.1.6 (archived 24 Sep 2026) | Both | Fixed | Move to 6.1.7 when you can | | 6.1.7 (archived 11 Nov 2026) | Both | Fixed; listed as "best available" | Read the release notes and behaviour changes first | Apache says 6.1.6 "disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled" ([pull request 171](https://github.com/apache/roller/pull/171)). Release dates are from the [Apache release archive](https://archive.apache.org/dist/roller/roller-6.1/); the [Roller downloads page](https://roller.apache.org/downloads/downloads.html) lists 6.1.7 as current and asks admins to read its release notes "including the behaviour changes, before upgrading a live site". ## Why the admin toggle does not help Roller has a setting in its administration interface that turns the XML-RPC blogging API off. It is natural to assume that closes the hole. Apache says it does not: "Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting." The September record for CVE-2026-82384 says the same thing in other words: the servlet "is mapped unconditionally, so parsing occurs even when the global XML-RPC feature is set to disabled; no non-default configuration is required". In plain terms, every unpatched Roller server is exposed, whether or not anyone uses XML-RPC. If you cannot upgrade today, Apache's interim mitigation is to **set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller**. Blocking that path at a reverse proxy or web application firewall in front of Roller is a reasonable extra layer while you do so. ## Timeline | Date | Event | Source | | --- | --- | --- | | 24 Sep 2026 | Roller 6.1.6 appears in the Apache release archive | Apache archive | | 25 Sep 2026 | Apache announces CVE-2026-82384: unauthenticated deserialization in the XML-RPC endpoint of Roller 6.1.5, fixed in 6.1.6; credits n0mi1k | Apache announcement, CVE record | | 11 Nov 2026 | Roller 6.1.7 appears in the Apache release archive | Apache archive | | 17 Nov 2026 | Apache announces CVE-2026-129448 for Roller 4.0.0 through 6.1.4: same flaw, "being actively exploited", admin toggle not enough; credits n0mi1k and Matt Raible | Apache announcement, CVE record | | 18 Nov 2026 | CISA's SSVC enrichment records "Exploitation: none"; the CVE is not in the KEV catalog released that day | CVE record, CISA KEV | ## What security leaders should do this week - Find every Roller server. Search for roller.war and Roller web application folders on Tomcat and other Java servers, check web logs for requests to /roller-services/, and ask teams that ran internal or community blogs. Roller sites are often old and unowned. - Upgrade to 6.1.6 or later, preferably 6.1.7 after reading its behaviour changes. If you cannot this week, apply Apache's web.xml change or remove the XML-RPC servlet mapping, restart, and block /roller-services/xmlrpc at the edge. Do not rely on the admin toggle. - Hunt on any server that was exposed. Apache says exploitation is happening and nobody has published when it started. Look for unusual POST requests to the XML-RPC path, the Java process starting shells or download tools, new files in the web application folders, new scheduled tasks and unexpected outbound connections. Review what the server could reach: its database credentials, any secrets in its configuration and the network around it. - If you find compromise, rebuild rather than clean, rotate the Roller database and admin credentials and anything else on the host, and run the response through the [IR Playbook Lab](/tools/ir-playbook-lab) if your team has not practised one. - Track it even though it is not in KEV yet. Watch the [KEV checker](/tools/kev-checker/CVE-2026-129448) for CISA's listing, and rank it now with the [vulnerability prioritizer](/tools/vulnerability-prioritizer): a vendor saying "actively exploited" is enough reason to act. Put any Roller server you cannot upgrade in your [risk register](/tools/risk-register) with an owner and a retirement date. ## Two Apache Java flaws in one week This follows the [Apache Axis 1.x flaw (CVE-2026-90436)](/blog/apache-axis-cve-2026-90436-exploited), which CISA added to KEV on 18 November alongside three others ([our KEV round-up](/blog/cisa-kev-synology-litellm-redcap-axis-november-2026)). Both are old Java components that process attacker-controlled data before any login check, both sit in software that tends to run for years without an owner, and in both cases a setting that looks like it should switch the feature off does not stop the parsing. The lesson for the patch programme is the same: inventory the old Java web applications, and verify a mitigation by testing it, not by reading the admin page. None of this is a breach of the Apache Software Foundation. See [Apache in the Breach Index](/breach-index/apache). ## Frequently asked questions ### What is CVE-2026-129448? A critical flaw in Apache Roller, the Java blog server. Per Apache's announcement of 17 November 2026, the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester, so an unauthenticated remote attacker can execute arbitrary code. It affects Roller 4.0.0 through 6.1.4 and is rated CVSS 3.1 9.8. ### Is CVE-2026-129448 being exploited? Apache says so. Its announcement states: "This issue is being actively exploited." Apache gives no details of who is exploiting it or how many sites are affected. It was not in CISA's Known Exploited Vulnerabilities catalog as of the 18 November 2026 catalog, and CISA's enrichment of the CVE record on 18 November recorded "Exploitation: none", which predates or does not reflect Apache's statement. ### How is CVE-2026-129448 related to CVE-2026-82384? Apache says they are the same vulnerability. CVE-2026-82384, published in September 2026, listed only Roller 6.1.5 as affected. CVE-2026-129448 covers the older releases, 4.0.0 through 6.1.4. The fix for both is Roller 6.1.6 or later. ### Which Apache Roller version fixes CVE-2026-129448? Roller 6.1.6 or later, which Apache says disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. The Roller downloads page lists 6.1.7 as the "best available" release, and Apache asks admins to read its release notes, including the behaviour changes, before upgrading a live site. ### Is disabling XML-RPC in the Roller admin page enough? No. Apache says: "Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting." Its interim mitigation is to set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. ### Who uses Apache Roller? Roller is a multi-user, Java-based blog server, often found running corporate, team or community blogs on Tomcat, sometimes for years without an owner. Search your estate for Roller deployments rather than assuming you have none. ### Was Apache hacked? No breach of the Apache Software Foundation is reported. CVE-2026-129448 is a vulnerability in Apache Roller software. The exposure is to organisations running an unpatched Roller server. ## Sources - [Apache: CVE-2026-129448, Apache Roller: unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5), announce@apache.org (17 November 2026)](https://lists.apache.org/thread/q573hvzrjyjvb5z600z8hgk044jqfshc) - [CVE.org: CVE-2026-129448 (CNA Apache Software Foundation; CISA ADP SSVC)](https://www.cve.org/CVERecord?id=CVE-2026-129448) - [Apache: CVE-2026-82384 announcement (25 September 2026)](https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9) and [CVE.org: CVE-2026-82384](https://www.cve.org/CVERecord?id=CVE-2026-82384) - [Apache Roller pull request 171 (the fix)](https://github.com/apache/roller/pull/171) - [Apache Roller downloads (6.1.7, "best available")](https://roller.apache.org/downloads/downloads.html) and [Apache release archive, Roller 6.1](https://archive.apache.org/dist/roller/roller-6.1/) - [CISA Known Exploited Vulnerabilities catalog (checked: not listed, catalog 2026.11.18)](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) - [NVD: CVE-2026-129448](https://nvd.nist.gov/vuln/detail/CVE-2026-129448)