Security notice
Run a site on Apache Roller? A flaw in the XML-RPC endpoint can let an unauthenticated attacker run code on the server. Apache says this is being actively exploited. Update to 6.1.6 or later today.
On November 17, 2026, the Apache Software Foundation published an advisory for CVE-2026-129448 in Apache Roller, a Java blogging platform. Apache rates it Critical, 9.8 on CVSS 3.1. The advisory says that in Apache Roller versions 4.0.0 through 6.1.4, an unauthenticated remote attacker can execute arbitrary code because the XML-RPC endpoint deserializes data before authenticating the requester. The advisory states: "This issue is being actively exploited." SecurityWeek, on November 19, also reported that statement from Apache's November 17 advisory, and said Apache did not provide further information about the attacks. Apache says this is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. The corrected affected range is 4.0.0 through 6.1.4. Apache recommends upgrading to Apache Roller 6.1.6 or later, which disables the extension types at issue and rejects XML-RPC requests when the XML-RPC feature is disabled. Apache Roller's download page lists 6.1.7 as the current "best available" general-availability release. Apache said 6.1.7 was released on November 11, 2026, and that it also includes other security fixes. If you cannot upgrade right away, Apache says to set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller. Apache also says disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. As of November 19, 2026, CISA Known Exploited Vulnerabilities Catalog (catalog version 2026.11.18, 1,786 entries when we checked) does not list CVE-2026-129448 or CVE-2026-82384. If you run Apache Roller, update to 6.1.6 or later today, with 6.1.7 the current release. EverThread does not test for this. (Apache advisory, Nov 17; SecurityWeek, Nov 19)
What happened
- The flaw. CVE-2026-129448 is described in an Apache advisory published November 17, 2026, to the oss-security list, from Arnout Engelen of the Apache Software Foundation. Apache says deserialization of untrusted data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The advisory says the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. (Apache advisory, Nov 17)
- Severity. Apache rates the issue Critical, CVSS 3.1 score 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). (Apache advisory, Nov 17)
- Apache says it is being exploited. The November 17 advisory states: "This issue is being actively exploited." That claim is Apache's. SecurityWeek, in a November 19 article, quoted the same sentence from the advisory and said Apache did not provide further information about the attacks. (Apache advisory, Nov 17; SecurityWeek, Nov 19)
- Earlier CVE number. Apache says this is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. The November 17 advisory corrects the affected range to 4.0.0 through 6.1.4. If you checked the earlier CVE and concluded only 6.1.5 was in scope, treat 4.0.0 through 6.1.4 as affected. (Apache advisory, Nov 17)
- The fix. Apache recommends upgrading to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. Apache Roller's download page lists 6.1.7 as the current "best available" general-availability release. Apache Roller's security page says 6.1.7 was released on November 11, 2026, and that it also fixes other vulnerabilities. SecurityWeek also noted that 6.1.7, released November 11, addresses other vulnerabilities. If you are updating, go to 6.1.7 unless you have a reason to stop at 6.1.6. (Apache advisory, Nov 17; Roller downloads; Roller security page)
- If you cannot upgrade right away. Apache says users who cannot upgrade right away should set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller. Apache also says disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. This is a temporary step, not a substitute for upgrading. (Apache advisory, Nov 17)
- CISA KEV. As of November 19, 2026, CISA's Known Exploited Vulnerabilities Catalog does not list CVE-2026-129448 or CVE-2026-82384. We checked the official JSON feed (catalog version 2026.11.18, dateReleased 2026-11-18T19:17:41.0354Z, 1,786 entries) about 8:23 AM ET on November 19, 2026. Apache's exploitation statement still stands even though the CVE is not in that catalog. (CISA KEV; Apache advisory, Nov 17)
Who should worry
Any website running Apache Roller 4.0.0 through 6.1.4. If you are already on 6.1.6 or 6.1.7, this CVE is fixed, though 6.1.7 is the current release and includes other security fixes. If you do not run Apache Roller, this notice does not apply to you.
What to do now
- Update to Apache Roller 6.1.6 or later today, with 6.1.7 the current release. Back up the site first. Download the current release from Apache Roller's download page and follow the project's upgrade notes. After the update, confirm the installed version. (Apache advisory, Nov 17; Roller downloads)
- If you cannot upgrade immediately, apply Apache's interim step, then plan the upgrade. Set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller. Do not rely on the administration UI setting that disables XML-RPC. Then schedule the upgrade to 6.1.6 or later. (Apache advisory, Nov 17)
- Review the site if it was reachable while unpatched. Apache says the issue is being actively exploited. If a vulnerable Roller site was on the internet after that advisory, have your developer, agency or host review the server and accounts. We are not claiming any tool, including EverThread, would have stopped an attack that used this flaw.
What to send your developer, agency or host
Apache Roller has CVE-2026-129448, an unauthenticated remote code execution flaw in the XML-RPC endpoint, affecting versions 4.0.0 through 6.1.4, rated 9.8 on CVSS 3.1 by Apache. Apache's November 17, 2026 advisory says: "This issue is being actively exploited." Apache also says this is the same vulnerability as CVE-2026-82384, which listed only 6.1.5 as affected. Please upgrade us to Apache Roller 6.1.6 or later today, preferably 6.1.7, which is the current release. If you cannot upgrade immediately, Apache says to set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough. After the update, confirm the installed version. Sources: Apache advisory, November 17, 2026; SecurityWeek, November 19, 2026; Apache Roller downloads.
Common questions
Does this mean my site was hacked?
No. A vulnerable version is a reason to update, or to apply Apache's interim step and then update, and to review the server if the site was reachable while unpatched. It is not, by itself, proof of a break-in. Apache's advisory says the issue is being actively exploited, but it does not say your site was involved.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see whether your site runs Apache Roller, which version it is on, or whether the XML-RPC endpoint is reachable. A scan without a warning about this software does not mean your site is safe.
Which version should I install?
Apache recommends 6.1.6 or later. 6.1.7 is the current "best available" general-availability release on Apache Roller's download page, released November 11, 2026, and it also includes other security fixes. Unless you have a reason to stop at 6.1.6, install 6.1.7.
Is this being exploited?
Apache's November 17, 2026 advisory states: "This issue is being actively exploited." That claim is Apache's. SecurityWeek quoted the same sentence and said Apache did not provide further information about the attacks. As of November 19, 2026, CISA's Known Exploited Vulnerabilities Catalog (catalog version 2026.11.18) does not list CVE-2026-129448 or CVE-2026-82384.
Is this the same as CVE-2026-82384?
Apache says yes: the November 17 advisory calls CVE-2026-129448 the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. The corrected affected range is 4.0.0 through 6.1.4.
Can I just turn off XML-RPC in the admin UI?
No. Apache says disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. The interim step Apache describes is to set enabledForExtensions to false in WEB-INF/web.xml, or to remove the /roller-services/xmlrpc servlet mapping, and restart Roller, then upgrade.
Where can I follow updates?
Follow the Apache advisory, Apache Roller's download page, Apache Roller's security page and CISA's Known Exploited Vulnerabilities Catalog.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- Apache advisory for CVE-2026-129448, November 17, 2026: oss-security post from Arnout Engelen (engelen@apache.org), dated November 17, 2026. Title: "CVE-2026-129448: Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)." Rates the issue Critical, CVSS 3.1 9.8. Affected versions: Apache Roller 4.0.0 through 6.1.4. States that an unauthenticated remote attacker can execute arbitrary code, that the XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester, that this is the same vulnerability as CVE-2026-82384 (which listed only 6.1.5 as affected), and that "This issue is being actively exploited." Recommends upgrading to 6.1.6 or later. Interim step: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, and restart Roller. Says disabling XML-RPC in the administration UI is not enough. Checked November 19, 2026.
- SecurityWeek, Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks, November 19, 2026: article by Eduard Kovacs, dated November 19, 2026, 7:13 AM ET. Reports Apache's confirmation of active exploitation of CVE-2026-129448, quotes "This issue is being actively exploited" from the November 17 advisory, and says Apache did not provide further information about the attacks. Notes the CVSS 9.8 rating, the 4.0.0 through 6.1.4 range, unauthenticated remote code execution, that disabling XML-RPC through the administration interface does not prevent exploitation, the earlier CVE-2026-82384 disclosure, the fix in 6.1.6, and that 6.1.7, released November 11, addresses other vulnerabilities. Checked November 19, 2026. This notice covers only the Roller CVE. It does not cover the separate Apache Axis issue discussed in the same article.
- Apache Roller Downloads: official download page listing Roller 6.1.7 as the current "best available" general-availability release, and directing readers to the 6.1.7 release notes before upgrading a live site. Checked November 19, 2026.
- Apache Roller Security page: official security page stating that Apache Roller 6.1.7 was released 11 November 2026 and that it fixes listed vulnerabilities, each of which affects 6.1.6 and, in most cases, earlier versions. Checked November 19, 2026.
- CVE-2026-129448 record at CVE.org: official CVE record linked from the Apache advisory. Checked November 19, 2026.
- CISA Known Exploited Vulnerabilities Catalog: official JSON feed at known_exploited_vulnerabilities.json, catalog version 2026.11.18, dateReleased 2026-11-18T19:17:41.0354Z, 1,786 entries when checked about 8:23 AM ET on November 19, 2026. CVE-2026-129448 and CVE-2026-82384 were not listed.