CISA added CVE-2026-129448 on November 20, 2026 for Apache Roller—unauthenticated deserialization on the /roller-services/xmlrpc endpoint. Apache's November 17 advisory rates CVSS 9.8 (Critical), states active exploitation, and covers versions 4.0.0 through 6.1.4. The same flaw was CVE-2026-82384 with a narrower version list; 6.1.6 is the fixed release line.
If a coding agent drops Roller into a Docker Tomcat stack or restores an old WAR for "internal blogging," this is unauthenticated RCE, not a commented-out feature flag.
Security champions should paste the CISA due date into the same channel where agents announce Friday deploys—when both land on the same weekend, humans must win the merge conflict over automation. A one-line pinned message beats a buried Jira sub-task.
TL;DR
| Question | Answer |
|---|---|
| Exploited? | Yes — Apache and CISA |
| Affected | Roller 4.0.0 – 6.1.4 |
| Fix | Upgrade to 6.1.6+ (6.1.7 current) |
| UI toggle enough? | No — deserialize runs first |
| KEV due | 2026-11-23 |
| Emergency | enabledForExtensions=false or remove xmlrpc servlet |
Mechanism step by step
From Apache's announce post:
- Client posts XML-RPC to Roller's vendor extension handler.
- Server deserializes extension types embedded in the request before authenticating the caller.
- Attacker-controlled serialized gadgets can yield arbitrary code execution in the Tomcat process.
Parser-ordering matches Apache Axis SOAP-fault RCE: fault or extension handling runs ahead of auth handlers operators assume protect the service.
Mitigations and upgrades
Preferred: upgrade to Apache Roller 6.1.6 or later per Apache. 6.1.7 (November 11, 2026) adds further fixes on the 6.1.6 base.
If you cannot upgrade immediately:
- Set
enabledForExtensionstofalseinWEB-INF/web.xml, or - Remove the
/roller-services/xmlrpcservlet mapping and restart Roller.
Apache explicitly warns that disabling XML-RPC in the administration UI is insufficient because vulnerable builds deserialize before that check.
Credit in the advisory: n0mi1k (finder), Matt Raible (reporter). Fix reference: GitHub PR #171.
What this means if you run AI coding agents
Roller is niche but appears in legacy intranet and academic deployments agents "modernize":
| Agent task | Risk |
|---|---|
docker compose Tomcat with old Roller WAR | Exposes xmlrpc if port published |
| Enable MetaWeblog for cross-posting | Turns on XML-RPC attack surface |
Copy web.xml from blog tutorial | May leave enabledForExtensions true |
Checks:
grep -R "roller-services/xmlrpc" .
grep -R "enabledForExtensions" WEB-INF/web.xml
Pin org.apache.roller versions in pom.xml agents edit; reject PRs that downgrade below 6.1.6.
Beam can scan skills and MCP configs before you run agent workflows and flag risky shell patterns on the laptop. It does not deserialize XML-RPC on your Roller server—patch or remove the servlet.
KEV and forensics
CISA lists CWE-502 (deserialization), forensic triage: Yes, due 2026-11-23. Pair patching with Tomcat access logs on /roller-services/xmlrpc and EDR on the host running Roller.
For wider Java deserialization context see Java4Shell discovery timelines and November KEV volume.
Timeline: CVE-2026-82384 to CVE-2026-129448
Understanding the two CVE IDs prevents agents from closing tickets too early:
| Date | Event |
|---|---|
| 24 Sep 2026 | Roller 6.1.6 release bundles fix for CVE-2026-82384 (XML-RPC deserialization) per security.html |
| 17 Nov 2026 | Apache widens affected range to 4.0.0–6.1.4, assigns CVE-2026-129448, confirms active exploitation |
| 18 Nov 2026 | Axis CVE-2026-90436 joins KEV—Java SOAP/XML surfaces under simultaneous pressure |
| 20 Nov 2026 | CISA KEV lists CVE-2026-129448, due Nov 23, forensics Yes |
Teams that patched only 6.1.5 when 82384 dropped may still run 4.x–6.1.4 elsewhere—inventory must be version-wide, not "we fixed last month's CVE."
Why the admin UI toggle fails (operator mental model)
Roller operators often disable XML-RPC in the administration UI believing the endpoint is dead. Apache's advisory is explicit: vulnerable builds deserialize extension types before evaluating that setting. The request path is roughly:
- HTTP POST hits
/roller-services/xmlrpc - XML parser handles vendor extensions
- Deserialization executes before auth and before feature flags that UI toggles affect
- Only then would disabled feature logic apply—too late for RCE
That ordering is why Apache recommends web.xml surgical changes or servlet removal, not checkbox configuration alone.
Detection and log fields
Without a public YARA from Apache, defenders use behavioral detection:
- Tomcat access logs showing POST to
/roller-services/xmlrpcfrom non-mgmt IPs - Spikes in 500 errors followed by new local users or unexpected WAR drops on the host
- Child processes from the Tomcat user unrelated to normal Roller cron jobs
- EDR Java gadget chains (Commons Collections, etc.) loading in the Tomcat PID
If an agent maintains Logback/Log4j configs, add a temporary alert rule on the xmlrpc path until 6.1.6+ is confirmed—then remove the rule to avoid noise.
Roller in agent-generated Java stacks
Roller is not a npm package; it appears as:
roller-webapp-*.wardropped intowebapps/- Maven dependency
org.apache.roller:roller-webapppinned in internal forks - Docker images built from tutorials where XML-RPC stays enabled for Windows Live Writer compatibility
Agents should treat Roller like any Java deserialization surface: add dependency-check or mvn versions:display-dependency-updates gates in CI templates they edit. When models propose "delete unused servlets," verify they remove xmlrpc mapping—not random auth filters.
Comparison to Apache Axis KEV (same week)
| Property | Axis CVE-2026-90436 | Roller CVE-2026-129448 |
|---|---|---|
| Protocol | SOAP Fault parsing | XML-RPC extensions |
| Auth timing | Before handler chain | Before XML-RPC auth |
| EOL status | Axis 1 EOL | Roller actively released (6.1.7) |
| UI mitigation | None credible | Insufficient (admin toggle) |
| Fix style | Commit/migrate | Upgrade to 6.1.6+ |
Both reward the same agent discipline: map legacy XML entrypoints before shipping refactors.
Forensic triage after suspected exploitation
CISA requires forensics for this KEV row. Practical steps on the app host:
- Preserve Tomcat
logs/and Roller DB backups before redeploying a clean WAR an agent builds. - Hash current
WEB-INF/lib—unexpected JARs indicate post-exploit persistence. - Review Roller user tables for new admin accounts or API keys.
- Correlate host timeline with VPN/firewall logs—unauthenticated RCE does not need stolen employee creds if port 8080 was exposed.
web.xml mitigation snippet (emergency)
Apache's advisory names enabledForExtensions. In the servlet configuration for XML-RPC, operators set:
<!-- Emergency only — upgrade to 6.1.6+ remains required -->
<init-param>
<param-name>enabledForExtensions</param-name>
<param-value>false</param-value>
</init-param>
Alternatively remove the entire servlet and servlet-mapping blocks for /roller-services/xmlrpc. Restart Tomcat and verify with a crafted POST attempt from an internal scanner—do not rely on UI screenshots alone. Agents editing web.xml should submit diffs for human review; a mistaken cut can disable unrelated auth filters.
Supply-chain and container rebuild loop
When Roller rides inside internal Helm charts:
- Bump base image Tomcat version only after Roller 6.1.6+ WAR is in the layer.
- Rescan registry tags agents promote—old
:latestmay still be 6.1.3. - Sign rebuilt images; attackers achieving RCE often plant pull secrets for registries agents use.
Link to LiteLLM and MCP CVE cluster for how agent gateways and Java blogging stacks sometimes share the same platform team on-call—one pager should not hide the other.
Reader checklist before closing the ticket
Work through this list in order—agents can assist, but a human should attest each line:
- Enumerate every host running Roller 4.0.0–6.1.4 (include forgotten lab VMs).
- Confirm build strings in WAR manifests or
RELEASE-NOTESinside the deployment. - Test whether
/roller-services/xmlrpcreturns anything other than 404 after mitigation. - Upgrade to 6.1.6+ on a canary Tomcat before fleet rollout.
- Re-run dependency scanners agents use in CI; add a fail build rule for affected GAV coordinates.
- Archive Tomcat logs for seven days pre-patch if CISA forensics applies to your sector.
- Document rollback: known-good WAR hash and
web.xmlbackup stored offline.
If any step fails, keep the incident bridge open—KEV exploitation plus unauthenticated RCE is not a next-sprint cleanup item.
Closing operational note
Apache Roller occupies an awkward niche in 2026: not as ubiquitous as WordPress, but still present in long-lived Java intranets that survived multiple platform migrations. Security teams sometimes forget Roller because it is not in the weekly npm audit digest coding agents run by default. That blind spot is why CISA's KEV listing matters politically—it elevates a blogging servlet to the same lane as vCenter and Cisco edge patches for federal contractors, which in turn pressures private-sector vendors who share Tomcat hosting with government clients.
From a defensive architecture standpoint, XML-RPC is a protocol from an era when desktop clients posted blogs remotely. Few legitimate 2026 workflows require it inside corporate networks. If product owners insist on keeping MetaWeblog compatibility, isolate Roller on a dedicated Tomcat instance with no lateral routes to ERP or identity systems, and terminate TLS at a WAF that can block extension types at the edge—understanding that WAF rules are compensating, not a substitute for 6.1.6+. For teams phasing Roller out entirely, agents can help export content to static sites, but the export project should not run concurrently with unpatched xmlrpc exposure; migrate content first or cut the servlet first.
Finally, when red teams test deserialization, they often chain Roller RCE to pivot toward internal Git or Jenkins on the same VM. Assume credential theft on the host if you see exploitation indicators, and rotate CI tokens stored on that machine even after patch. The deserialization bug is the entry; lateral movement is the business impact coding agents should model in tabletop exercises.
Register this item in your agent patch backlog with explicit acceptance criteria: xmlrpc returns 404, Roller version ≥ 6.1.6, and forensic log archive uploaded if required. Vague "Tomcat updated" tickets invite regression when agents rebuild images from stale layers next sprint. Schedule a quarterly rediscover scan for xmlrpc paths in internal DNS names—Roller instances often hide under blog.internal.* hostnames that CMDBs omit.
Frequently asked questions
Is Apache Roller still maintained?
Yes. Security fixes ship on the current release line only—roller.apache.org/security.html documents 6.1.6 and 6.1.7 advisories.
Does CVE-2026-129448 need authentication?
No — unauthenticated remote attack per Apache.
What servlet path is vulnerable?
/roller-services/xmlrpc — remove or harden per advisory.
Related reading
- Apache Axis KEV SOAP fault RCE
- Mongoose query injection
- VMware vCenter KEV auth bypass
- Prompt injection and capability security
Primary sources: Apache announce thread, Roller security page, CISA KEV, GHSA-pxp4-phq9-fx2q
Advisory details are accurate as of November 20, 2026 per Apache and CISA publications.

