Are your Apache Roller servers exposed to unauthenticated remote code execution?
Apache's 17 November 2026 CVE record and mailing-list announcement describe an unauthenticated remote code execution flaw in the XML-RPC endpoint of Apache Roller. The endpoint accepts vendor extension types and deserializes them before authenticating the requester. CVE-2026-129448 covers versions 4.0.0 through 6.1.4. Apache says this is the same vulnerability as CVE-2026-82384, which listed only 6.1.5 as affected. Apache, as the CNA, scores it CVSS 3.1 9.8 Critical, and says the issue is being actively exploited. Upgrade to Roller 6.1.6 or later.
Critical (CVSS 9.8). Actively exploited, according to Apache. Not in CISA KEV
Apache's 17 November 2026 record and announcement say: "This issue is being actively exploited." On the same CVE.org record, CISA's ADP Vulnrichment entry (dated 11:26 GMT on 17 November 2026) still lists Exploitation as "none". Apache does not publish detail of the attacks or when they started. Upgrade to Apache Roller 6.1.6 or later. The Roller downloads page currently lists 6.1.7 as "best available". If you cannot upgrade right away, 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. CVE-2026-129448 and CVE-2026-82384 were not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 11:35 GMT on 17 November 2026 (catalogue 2026.11.13, released 20:24 GMT on 13 November 2026). Recheck KEV. We report Apache's statement and the CISA ADP value together. We do not treat the CISA ADP value, or the absence from KEV, as contradicting Apache's statement that the issue is being actively exploited. We do not link proof-of-concept or exploit code.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 18 November 2026, 18:09 GMT.
At a Glance
Based on the CVE.org and NVD records for CVE-2026-129448, the CVE.org record for CVE-2026-82384, Apache's 17 November 2026 announcement, Apache's 25 September 2026 announcement for CVE-2026-82384, Apache Roller pull request 171, and the Roller downloads page, checked at 11:35 GMT and rechecked at 12:00 GMT on 17 November 2026. CISA KEV catalogue 2026.11.13 was also checked at that time. Last updated 18 November 2026, 18:09 GMT.
Critical, CVSS 3.1 9.8
Apache, as the CNA, scores CVE-2026-129448 and CVE-2026-82384 CVSS 3.1 9.8 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502). The 17 November 2026 announcement also labels the severity Critical. NVD's copy of CVE-2026-129448 was still in Received status when we checked at 11:35 GMT on 17 November 2026, and NVD has not published its own score. The earlier NVD record for CVE-2026-82384 had status Deferred when we checked.
Actively exploited, according to Apache; not in CISA KEV
Apache's 17 November 2026 record and announcement say the issue is being actively exploited. On the same CVE.org record, CISA's ADP Vulnrichment entry (dated 11:26 GMT on 17 November 2026) still lists Exploitation as "none". Apache does not publish detail of the attacks or when they started. CVE-2026-129448 and CVE-2026-82384 were not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 11:35 GMT on 17 November 2026 (catalogue 2026.11.13, released 20:24 GMT on 13 November 2026). Recheck KEV. We report Apache's statement and the CISA ADP value together. We do not treat the CISA ADP value, or the absence from KEV, as contradicting Apache's statement.
Roller 4.0.0 through 6.1.5
CVE-2026-129448 covers Apache Roller 4.0.0 through 6.1.4 (Apache also writes this as 4.0.0 before 6.1.5). CVE-2026-82384 covers 6.1.5 only. Taken together, 4.0.0 through 6.1.5 are affected. Apache does not say whether versions before 4.0.0 are affected. The path named in Apache's workaround is /roller-services/xmlrpc.
Upgrade to Roller 6.1.6 or later
Apache recommends Apache Roller 6.1.6 or later, which is the minimum fix, and which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. The Roller downloads page, checked at 12:00 GMT on 17 November 2026, lists 6.1.7 as the "best available" general availability release, and asks readers to read the 6.1.7 release notes, including the behaviour changes, before upgrading a live site. Apache cites pull request 171 as the patch (merged 5 September 2026). A workaround is available if you cannot upgrade right away; turning XML-RPC off in the administration UI is not enough.
Apache Roller pull request 171, "Disable vendor extension types on the XML-RPC servlet", is merged. Apache later cites this pull request as the patch.
Apache announces CVE-2026-82384, covering Apache Roller 6.1.5 only, and recommends upgrading to 6.1.6 or later.
Apache announces CVE-2026-129448 at 11:02 GMT, widening the affected range to 4.0.0 through 6.1.4, and says the issue is being actively exploited. CVE.org publishes the record at 11:03 GMT. NVD publishes its copy at 11:17 GMT, with status Received.
Upgrade to 6.1.6 or later (the Roller downloads page lists 6.1.7 as "best available"), or apply Apache's workaround and restart. Until you have patched, block POST requests to /roller-services/xmlrpc at the proxy or WAF, and hunt the patterns below from 25 September 2026.
What to Do in the Next 24 Hours
Proactive on the left. Reactive on the right. Vendor steps and our advice are labelled separately.
Upgrade, or apply the workaround
- Vendor advice: upgrade to Apache Roller 6.1.6 or later, the minimum fix, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. The downloads page currently lists 6.1.7 as "best available".
- Vendor advice: if you cannot upgrade right away, 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, because older versions deserialize the request before checking that setting.
- Our advice: inventory every Apache Roller install you or your clients run. Treat internet-facing 4.0.0 through 6.1.5 as exposed.
- Our advice: until you have patched, block POST requests to
/roller-services/xmlrpcat the proxy or WAF.
Hunt and contain
- Our advice: Apache does not publish indicators of compromise. The hunts below are our patterns, labelled OUR PATTERN, not vendor IOCs.
- Our advice: hunt from 25 September 2026 (our start date) for POST requests to
/roller-services/xmlrpcthat carry Java-serialized data (base64rO0AB), for Tomcat or Java spawning a shell, for new JSP files or webshells under the web application, and for unexpected outbound connections. These are OUR PATTERN hunts, not vendor IOCs. - Our advice: a hunt hit is a lead to investigate, not proof that code ran.
- Our advice: if you find a compromise, isolate the host, keep the logs, rotate the credentials Roller holds, and rebuild on 6.1.6.
Proactive: Vendor Advice, Then Ours
Apache's official advice first. CybaVerse advice is labelled separately.
Upgrade to Apache Roller 6.1.6 or later
Apache recommends upgrading to Apache Roller 6.1.6 or later, the minimum fix, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. This is the fix for both CVE-2026-129448 (4.0.0 through 6.1.4) and CVE-2026-82384 (6.1.5). The Roller downloads page currently lists 6.1.7 as "best available". Apache cites pull request 171 as the patch.
Workaround if you cannot upgrade yet
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. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.
Inventory Roller and treat exposed installs as urgent
Find every Apache Roller install you or your clients run, and check the version. Treat any internet-facing 4.0.0 through 6.1.5 instance as exposed. Look for the /roller-services/xmlrpc path named in Apache's workaround. Upgrade those installs to 6.1.6 or later; 6.1.7 is listed as "best available" on the downloads page. Apache does not say whether versions before 4.0.0 are affected.
Block POST to the XML-RPC path until patched
Until you have upgraded, block POST requests to /roller-services/xmlrpc at the proxy or WAF. If you cannot upgrade immediately, also apply Apache's workaround and restart. The proxy or WAF block is our advice, in addition to the vendor workaround.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only. Pack version 1.0.0 is the download on this page. The KQL and Sigma have not been run against live data.
check-roller.sh
Read-only offline checker, pack version 1.0.0. Unpack the full pack first, so scripts/ stays in place. It opens no sockets and writes nothing. It only reads WEB-INF/web.xml and WEB-INF/classes/roller-version.properties under the webapp folder you name. It never reads passwords. For Roller 4.0 installs, pass --version: the pack README says those builds store the version inside a jar, so the properties file may be absent.
bash scripts/check-roller.sh --webapp /path/to/tomcat/webapps/ROLLER_APP
# Roller 4.0, or any install with no readable roller-version.properties
bash scripts/check-roller.sh --webapp /path/to/tomcat/webapps/ROLLER_APP --version 4.0.0Check-Roller.ps1
The same checks in PowerShell 7, with identical output and exit codes. Run it from the unpacked full pack. It is also read-only and does not use the network.
pwsh -File scripts/Check-Roller.ps1 -Webapp /path/to/tomcat/webapps/ROLLER_APP
pwsh -File scripts/Check-Roller.ps1 -Webapp /path/to/tomcat/webapps/ROLLER_APP -Version 4.0.0KQL and Sigma
9 KQL hunts for Microsoft Sentinel and Defender, all OUR PATTERN, looking back from 25 September 2026 (our start date; Apache does not publish when exploitation began). Q1 looks for POST requests to /roller-services/xmlrpc. Q2 looks for Java-serialized data (rO0AB) in logged request content (field availability unverified). Q3 and Q3b look for Tomcat or Java spawning a shell. Q4 looks for new JSP files under a webapps folder. Q5 looks for unexpected outbound connections. Q6, Q6b and Q6c inventory Roller exposure (Q6b and Q6c unverified telemetry). 7 Sigma rules, all OUR PATTERN, with Kusto conversions included. The KQL and Sigma have not been run against live data. A hunt hit is a lead to investigate, not proof that code ran.
Verdicts
- FIXED6.1.6 or later, and the XML-RPC extension types are not switched on (exit 0).
- VULNERABLE4.0.0 to 6.1.5, with
enabledForExtensionson and the XML-RPC servlet mapped (exit 1). - MITIGATED, UPGRADE NEEDED4.0.0 to 6.1.5, with Apache's workaround in place (exit 2).
- REVIEW6.1.6 or later, but
web.xmlstill has the extension types on and the servlet mapped (exit 3). - UNKNOWNVersion not found, not a plain number, or below 4.0.0, which Apache does not state either way (exit 4).
Exit codes
| Code | Meaning |
|---|---|
| 0 | FIXED |
| 1 | VULNERABLE |
| 2 | MITIGATED, UPGRADE NEEDED |
| 3 | REVIEW (fixed, but extension types still on) |
| 4 | UNKNOWN |
| 5 | Usage or read error |
The full pack zip contains 60 files (pack version 1.0.0). The checker never fetches anything and never prints file contents beyond the version number, the XML-RPC servlet and filter names, and their URL patterns.
Know the limits
- Both checkers are read-only and offline. They only read
WEB-INF/web.xmlandWEB-INF/classes/roller-version.propertiesunder the webapp folder you point them at. They send no network traffic, write nothing and contain no exploit payloads. - Apache's records publish no indicators of compromise. Every hunt and Sigma rule in this pack is OUR PATTERN, not a vendor IOC.
- A hunt hit is a lead to investigate. It does not prove that code ran.
- The hunts look back from 25 September 2026. That start date is our choice, because Apache does not publish when exploitation began.
- None of the KQL or Sigma has been run against live data. Q2 (logged request content), Q6b and Q6c are marked unverified in the pack README and depend on your connectors.
- Prefer the hand-written KQL. Some Sigma pipeline conversions fail, as the pack README explains.
What is in the pack
| File | What it does |
|---|---|
| scripts/check-roller.sh | Offline web.xml and version checker for Linux and macOS (bash) |
| scripts/Check-Roller.ps1 | The same checker in PowerShell 7 |
| KQL (9 hunts) | Microsoft Sentinel and Defender hunts Q1 to Q6c, all OUR PATTERN, from 25 September 2026 |
| Sigma (7 rules) | All OUR PATTERN, plus Kusto conversions |
| tests/ | Fixtures, bash and Pester tests and a sandboxed no-network run |
| README.md | Verified facts, vendor vs our advice, checker usage, limits and sources |
Reactive: How to Hunt (Our Advice)
Apache's records do not publish indicators of compromise. The hunts below are CybaVerse advice, labelled OUR PATTERN, not vendor IOCs, and they look back from 25 September 2026 (our start date). CybaOps can run them across your estate. A hunt hit is a lead to investigate, not proof that code ran. The KQL and Sigma in the pack have not been run against live data.
Q1 and Q2: POST requests to the XML-RPC path, including Java-serialized data
Pack hunt Q1 looks for POST requests to /roller-services/xmlrpc, including large bodies. Q2 looks for Java-serialized data (base64 rO0AB) in logged request content; field availability for Q2 is unverified. Apache does not publish these patterns; they are our hunts, not vendor IOCs.
Q3 and Q3b: Tomcat or Java spawning a shell
Pack hunts Q3 and Q3b look for the Tomcat or Java process spawning a shell, such as sh, bash, cmd or PowerShell. This is our pattern, not a vendor IOC.
Q4: New JSP files or webshells
Pack hunt Q4 looks for new JSP files under a webapps folder. This is our pattern, not a vendor IOC.
Q5: Unexpected outbound connections
Pack hunt Q5 looks for unexpected outbound connections from hosts that look like Roller servers. This is our pattern, not a vendor IOC. Q6, Q6b and Q6c inventory exposure (Q6b and Q6c unverified telemetry).
If you find a compromise (our advice)
- Isolate the host from untrusted networks and keep the logs.
- Rotate the credentials Roller holds, including database and other integration credentials.
- Rebuild the service on Apache Roller 6.1.6 or later, rather than only patching a compromised install in place.
- Review traffic from the host for unexpected destinations, and start incident response if the host can reach wider management or production networks.
Apache Roller CVE-2026-129448 FAQ
Short answers based on the CVE.org and NVD records, Apache's 17 November 2026 announcement, Apache's 25 September 2026 announcement for CVE-2026-82384, and pull request 171, rechecked at 11:35 GMT on 17 November 2026.
What is CVE-2026-129448, and how does it relate to CVE-2026-82384?
Apache's 17 November 2026 CVE record and mailing-list announcement describe CVE-2026-129448 as deserialization of untrusted data in Apache Roller versions 4.0.0 through 6.1.4 that allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. Apache says this is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. The earlier Apache announcement for CVE-2026-82384, dated 25 September 2026, covers 6.1.5 only. Apache cites pull request 171 as the patch.
How severe is it?
Apache, as the CNA, scores both CVE-2026-129448 and CVE-2026-82384 CVSS 3.1 9.8 Critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502 (Deserialization of Untrusted Data). The 17 November 2026 announcement also labels the severity Critical. NVD's copy of CVE-2026-129448 was still in Received status when we checked at 11:35 GMT on 17 November 2026, and NVD has not published its own score. The earlier NVD record for CVE-2026-82384 had status Deferred when we checked.
Is it being exploited, and is it in CISA KEV?
Apache's 17 November 2026 CVE record and announcement say: "This issue is being actively exploited." On the same CVE.org record, CISA's ADP Vulnrichment entry (dated 11:26 GMT on 17 November 2026) still lists Exploitation as "none". Apache does not publish detail of the attacks or when they started. CVE-2026-129448 and CVE-2026-82384 were not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 11:35 GMT on 17 November 2026 (catalogue 2026.11.13, released 20:24 GMT on 13 November 2026). Recheck KEV. We report Apache's statement and the CISA ADP value together. We do not treat the CISA ADP value, or the absence from KEV, as contradicting Apache's statement that the issue is being actively exploited.
Which versions are affected?
CVE-2026-129448 covers Apache Roller 4.0.0 through 6.1.4. Apache's announcement also writes this range as 4.0.0 before 6.1.5. CVE-2026-82384 covers Apache Roller 6.1.5 only. Taken together, 4.0.0 through 6.1.5 are affected. Apache does not say whether versions before 4.0.0 are affected. The minimum fix is 6.1.6 or later. The Roller downloads page currently lists 6.1.7 as "best available".
What is Apache's official advice?
Vendor advice: Apache recommends upgrading to Apache Roller 6.1.6 or later, the minimum fix, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. 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. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. Apache cites pull request 171 as the patch.
What is CybaVerse's advice?
Our advice: inventory every Apache Roller install you or your clients run, and treat internet-facing 4.0.0 through 6.1.5 as exposed. Upgrade to 6.1.6 or later; the downloads page lists 6.1.7 as "best available". Until you have patched, block POST requests to /roller-services/xmlrpc at the proxy or WAF. If you cannot upgrade immediately, apply Apache's workaround and restart. If you find a compromise, isolate the host, keep the logs, rotate the credentials Roller holds, and rebuild on 6.1.6. The hunt patterns on this page are our patterns, not vendor indicators.
Who is this relevant to?
Organisations and MSPs that run Apache Roller, especially any install whose /roller-services/xmlrpc endpoint is reachable from the internet or from a network that is not fully trusted, on versions 4.0.0 through 6.1.5.
Where do we get official updates?
Watch the CVE.org record for CVE-2026-129448, the CVE.org record for CVE-2026-82384, the NVD record for CVE-2026-129448, Apache's 17 November 2026 announcement, and Apache's earlier 25 September 2026 announcement for CVE-2026-82384. The Roller downloads page lists the current best-available release. Recheck CISA KEV.
Need help finding Apache Roller across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions. The CybaOps Remediation Engine is live: it can fix security issues automatically, so gaps get closed rather than just reported. CybaRemediate, our remediation product line built on the Remediation Engine, is live. Book a CybaOps demo and see the Remediation Engine close a gap.
Sources
- CVE.org: CVE-2026-129448 (CNA: Apache; CVSS 3.1 9.8 Critical, CWE-502; published 17 November 2026, 11:03 GMT)
- NVD: CVE-2026-129448 (CNA: Apache; CVSS 3.1 9.8 Critical, CWE-502; published 17 November 2026, 11:17 GMT; status Received when checked at 11:35 GMT on 17 November 2026)
- Apache mailing-list announcement for CVE-2026-129448 (dated 17 November 2026, 11:02 GMT)
- CVE.org: CVE-2026-82384 (CNA: Apache; CVSS 3.1 9.8 Critical, CWE-502; published 28 September 2026)
- Apache mailing-list announcement for CVE-2026-82384 (25 September 2026)
- Apache Roller pull request 171, Disable vendor extension types on the XML-RPC servlet (merged 5 September 2026)
- Apache Roller downloads page (6.1.7 listed as "best available" when checked at 12:00 GMT on 17 November 2026)