Skip to content
eastbaycyber

CVE-2026-129448: Apache Roller XML-RPC RCE

CVSS · Critical
9.8
In CISA KEV
Yes
Published
Nov 17
Patch SLA & TriageVector: Network
Immediate (BOD 22-01 due 2026-11-23)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 9.8
Decode Vector & Sub-Scores →
CVE explainers 12 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-17
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-20. Federal agencies must patch by 2026-11-23.

Everything CISA added on 2026-11-20 · Apache KEV history

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-129448 is a critical Apache Roller deserialization flaw enabling unauthenticated remote code execution through XML-RPC. - Apache Roller 4.0.0 through 6.1.5 are affected; upgrade to 6.1.6 or later. - The NVD reports active exploitation. Restrict XML-RPC and investigate exposed systems immediately.

CVE-2026-129448 is a critical Apache Roller vulnerability involving unsafe XML-RPC deserialization. An unauthenticated remote attacker may be able to execute arbitrary code on a vulnerable Roller server. Organizations should prioritize internet-facing deployments, investigate requests to the XML-RPC endpoint, and upgrade to Apache Roller 6.1.6 or later.

Vulnerability at a Glance

CVE-2026-129448 affects Apache Roller’s XML-RPC endpoint. The issue is classified as CWE-502, deserialization of untrusted data. Attacker-controlled XML-RPC data is processed before authentication, creating a path to arbitrary code execution without valid Roller credentials.

Field Details
CVE ID CVE-2026-129448
CVSS 9.8 critical
CVSS vector Not supplied in the available NVD response; confirm the authoritative record before publication
Attack vector Network
Authentication required None
Privileges required None
User interaction None indicated
Impact Potential arbitrary code execution on the Roller server
Affected versions Apache Roller 4.0.0 through 6.1.5, combining the available records
Fixed version Apache Roller 6.1.6 or later
Patch available Yes
CISA KEV status Not listed
Exploitation NVD reports active exploitation

The patch status is straightforward: an upstream fixed release is available, but systems running older Roller versions remain exposed unless the XML-RPC processing path is removed or disabled through the documented deployment configuration.

The available research identifies CVE-2026-129448 as related to CVE-2026-82384. The latter record identified Apache Roller 6.1.5, while CVE-2026-129448 expands the affected range to earlier releases. Administrators should treat Roller 4.0.0 through 6.1.5 as vulnerable until the deployment is upgraded or technically mitigated.

Analyst’s Take: Upgrade internet-facing Roller deployments first, then apply the configuration-level workaround where patching cannot happen immediately. The NVD reports active exploitation, while the available research does not identify a verified public proof-of-concept repository. Do not use the absence of public exploit code to delay containment or investigation.

What Is This Vulnerability?

The root cause is unsafe deserialization of attacker-controlled data in Apache Roller’s XML-RPC endpoint. The endpoint accepts vendor extension types and processes the supplied data before authenticating the requester. An unauthenticated remote attacker can send a crafted request to a reachable Roller service and potentially cause arbitrary code execution in the privileges of the application server.

This pre-authentication processing is the key operational detail. A normal application-level control, such as disabling XML-RPC through the Roller administration interface, may be evaluated too late on affected older releases. The vulnerable servlet can parse input before the application checks the global XML-RPC setting, leaving the attack surface reachable despite an apparent administrative disablement.

The issue is also described as related to CVE-2026-82384. The relationship matters for asset review because teams that previously assessed only Roller 6.1.5 may overlook older releases. The combined information indicates that the vulnerable range is Apache Roller 4.0.0 through 6.1.5, with remediation in 6.1.6.

A successful exploit could provide code execution on the server hosting Roller. The resulting impact depends on the operating-system account, Java process permissions, network access, secrets available to the application, and whether the server hosts other applications. Potential consequences include web-application modification, credential theft, persistence, lateral movement, data access, and use of the server for additional attacks.

For background on how vulnerability records can describe related issues, see our CVE-2016-3081 analysis.

AnalystImpact · assess the risk

Who Is Affected?

The affected product is Apache Roller, an open-source Java blogging and content-management platform. The available vulnerability description identifies Apache Roller versions 4.0.0 through 6.1.4 as affected by CVE-2026-129448. The related CVE record separately identifies 6.1.5, so defenders should use the combined range 4.0.0 through 6.1.5 for exposure assessment.

Vendor Product Affected range Fixed release
Apache Software Foundation Apache Roller 4.0.0 through 6.1.5 6.1.6 or later

Internet-facing Roller installations are the highest-priority targets, particularly where the /roller-services/xmlrpc path is accessible from untrusted networks. Internal deployments still require review: a compromised workstation, VPN account, cloud workload, or adjacent application may provide network access to an internal Roller instance.

Teams should account for packaged or customized deployments. A version may be embedded in a WAR file, container image, appliance, or vendor-managed platform rather than installed as a clearly labeled system package. Verify the actual Roller application version and inspect the deployed servlet configuration. A system that reports an administratively disabled XML-RPC feature may still require configuration-level mitigation if it runs an affected release.

CVSS Score Breakdown

CVE-2026-129448 has a reported CVSS score of 9.8, placing it in the critical severity category. The available NVD response does not include the complete CVSS vector string, so the exact metric values should be confirmed against the authoritative CVE record before being reproduced as a formal vector.

The described attack characteristics indicate a network-reachable vulnerability requiring no authentication, no privileges, and no user interaction. The reported impact is consistent with high confidentiality, integrity, and availability impact because arbitrary code execution can allow an attacker to read data, alter application or host content, and disrupt services.

Metric Assessment from available description Operational meaning
Attack vector Network The attacker can reach the vulnerable endpoint remotely
Attack complexity Low, based on described characteristics Exploitation does not appear to require unusual conditions
Privileges required None A valid Roller account is not required
User interaction None No victim action is indicated
Confidentiality High impact indicated Server and application data may be exposed
Integrity High impact indicated Files, application content, or data may be modified
Availability High impact indicated The service or host may be disrupted

Do not infer that the absence of a CVSS vector makes the risk uncertain. CVSS is a severity framework, not a measure of whether a vulnerability is currently being attacked. Here, the NVD description explicitly reports active exploitation, making exposure and exploitability more urgent than the numeric score alone suggests.

Exploitation Status

The NVD description states that CVE-2026-129448 is being actively exploited. This is a report of exploitation in the wild and should drive immediate prioritization for internet-facing Roller systems. Organizations should assume that an exposed, unpatched instance may already have received malicious requests, even if application logs do not clearly identify exploitation.

The available research did not identify a verified public proof-of-concept repository. The principal GitHub reference is Apache Roller pull request #171, which documents the upstream fix rather than providing a confirmed exploit. “No verified public PoC identified” must not be interpreted as “not exploitable”; the NVD exploitation statement is the stronger operational signal.

CVE-2026-129448 is not currently listed in the CISA Known Exploited Vulnerabilities catalog. The available lookup returned on_kev: false, with no CISA due date, required action, or ransomware-campaign designation. KEV status and exploitation status are separate signals: absence from KEV does not contradict the NVD report of active exploitation.

Preserve evidence before making disruptive changes where feasible. Capture relevant reverse-proxy, web-server, application, host, process, and network telemetry, then contain the endpoint and patch the system. Investigate suspicious activity even when no public exploit code is available.

ResponderRunbook · act now

How to Detect It

Start by identifying every Apache Roller deployment and determining whether the XML-RPC endpoint is reachable. Search reverse-proxy and web-server logs for requests to /roller-services/xmlrpc, especially unauthenticated POST requests from external addresses. The path alone is not proof of exploitation, but it is a high-value triage indicator when combined with unusual request bodies, repeated failures, unexpected response codes, or activity from scanning infrastructure.

Review host telemetry around requests to the endpoint. A successful exploit may be followed by Java child processes, shells, download utilities, outbound connections, newly created files, modified WAR or JSP content, scheduled tasks, service changes, or access to application secrets. Look for activity under the account running the Java application server, and compare process, file, and network behavior with a known-good baseline.

Technical Notes: Web and Network Detection

A basic web-log search can identify requests to the vulnerable path:

grep -Ei 'POST[[:space:]]+/[^[:space:]]*/roller-services/xmlrpc([/?[:space:]])' \\
  /var/log/nginx/access.log /var/log/httpd/access_log 2>/dev/null

For environments using a SIEM, a generic query should be adapted to the local schema:

http.request.method = "POST"
AND url.path endswith "/roller-services/xmlrpc"

Prioritize events where the request is unauthenticated or originates outside trusted administration networks:

http.request.method = "POST"
AND url.path endswith "/roller-services/xmlrpc"
AND (user.name IS NULL OR user.name = "-" OR src.ip NOT IN trusted_admin_ranges)

The XML-RPC endpoint commonly carries XML in the request body. A network sensor can therefore flag POST requests to the path with XML content types for investigation:

http.method == "POST" &&
http.uri contains "/roller-services/xmlrpc" &&
(http.content_type contains "xml" || http.request_body contains "<?xml")

These are triage signatures, not complete exploit signatures. They may generate false positives from legitimate XML-RPC clients, and they cannot reliably identify serialized payloads without application-aware parsing. Correlate them with process execution, outbound network activity, file changes, and authentication or administrative events.

Host-Based Investigation

Inspect child processes created by the Java process that hosts Roller. Examples include shells, scripting runtimes, archive tools, network clients, and interpreters that are not expected in normal Roller operation:

ps -eo pid,ppid,user,lstart,args --forest
pstree -ap "$(pgrep -n -f 'java.*roller')"

Review recently modified application and temporary files, adjusting paths for the local deployment:

find /opt/roller /var/lib/tomcat /tmp -type f -mmin -1440 \\
  -printf '%TY-%Tm-%Td %TH:%TM:%TS %u %p\\n' 2>/dev/null

Also review outbound connections from the application host and examine shell history, service definitions, cron entries, and web-application directories. Detection should focus on the full post-exploitation chain rather than relying on a single request pattern.

Mitigation and Patching

The recommended fix is to upgrade to Apache Roller 6.1.6 or later. Confirm the target release through the official Apache Roller distribution and validate the deployed application after replacement. Restart the application server so the corrected classes and servlet configuration are loaded; a file copied into the deployment directory without a complete restart may leave vulnerable code resident in memory.

A generic deployment workflow for a WAR-based installation might look like this, but administrators must substitute their organization’s approved artifact URL, service name, and deployment paths:

# Stop the application server
sudo systemctl stop tomcat

# Back up the current deployment and configuration
sudo cp -a /var/lib/tomcat/webapps/roller \\
  /var/backups/roller-$(date +%Y%m%d-%H%M%S)

# Deploy the verified Apache Roller 6.1.6-or-later artifact
sudo cp apache-roller-6.1.6.war /var/lib/tomcat/webapps/roller.war

# Start the application server
sudo systemctl start tomcat

# Confirm service health and inspect startup logs
sudo systemctl status tomcat --no-pager
sudo journalctl -u tomcat -n 200 --no-pager

Do not copy this command sequence blindly into production. Verify the release checksum or signature according to the organization’s software-supply-chain process, preserve configuration and data, test the upgrade in a representative environment, and confirm that the running application reports the intended version.

Technical Notes: Temporary Workarounds

If immediate upgrading is impossible, the available advisory information recommends setting enabledForExtensions to false in WEB-INF/web.xml, or removing the /roller-services/xmlrpc servlet mapping. A configuration-level change should be followed by an application-server restart:

sudo cp -a /path/to/roller/WEB-INF/web.xml \\
  /path/to/roller/WEB-INF/web.xml.bak.$(date +%Y%m%d-%H%M%S)

# Edit the deployment descriptor and set the extension setting to false.
sudo vi /path/to/roller/WEB-INF/web.xml

# Restart the service after the change.
sudo systemctl restart tomcat

If the deployment uses a WAR file, edit the source or build configuration and redeploy rather than making an ephemeral change inside an exploded directory that may be overwritten. Alternatively, remove the servlet mapping for /roller-services/xmlrpc from the deployment descriptor, then restart Roller. Validate the result from an external test network:

curl -i -X POST https://roller.example.com/roller-services/xmlrpc \\
  -H 'Content-Type: text/xml' \\
  --data '<?xml version="1.0"?><methodCall><methodName>system.listMethods</methodName><params/></methodCall>'

The endpoint should no longer provide the vulnerable service. The exact expected HTTP status depends on the front-end and application configuration, so treat a blocked or unmapped response as a validation signal rather than relying on one status code.

Do not rely solely on the XML-RPC disablement control in the Roller administration interface on affected older versions. The vulnerable parsing can occur before that application-level setting is checked. Apply the web.xml workaround or remove the servlet mapping, restrict access at the reverse proxy or firewall, and upgrade as soon as possible.

Network controls can provide additional containment:

location = /roller-services/xmlrpc {
    deny all;
    return 403;
}

Deploy this only after confirming that the exact path and proxy behavior match the local installation. Access restrictions reduce exposure but do not remove a compromise that may already have occurred. After patching, review logs and host telemetry for signs of exploitation, rotate credentials that may have been accessible to the application, and assess whether the server requires reimaging if unauthorized code execution is confirmed.

Incident Response Checklist

If you identify suspicious XML-RPC requests or post-exploitation activity:

  1. Preserve relevant logs, memory, process data, and network telemetry where practical.
  2. Restrict access to /roller-services/xmlrpc at the reverse proxy or firewall.
  3. Isolate the host if code execution or persistence is suspected.
  4. Upgrade to Apache Roller 6.1.6 or later.
  5. Review Java child processes, modified files, scheduled tasks, services, and outbound connections.
  6. Rotate credentials and secrets accessible to the Roller process.
  7. Check connected systems for lateral movement or reused credentials.
  8. Reimage the server when compromise cannot be confidently contained and eradicated.
  9. Document affected assets, timeline, indicators, and remediation evidence.

References

The NVD record for CVE-2026-129448 is the primary source for the reported CVSS score, affected-version description, exploitation statement, and mitigation details:

The related CVE record identifies Apache Roller 6.1.5 in connection with the same underlying issue and should be reviewed alongside CVE-2026-129448:

Apache Roller’s upstream change is documented in pull request #171. This reference describes the fix and is not a verified public exploit repository:

Additional Apache disclosure and mailing-list references are available at:

CISA KEV status should be checked independently because catalog membership can change. At the time covered by this article, CVE-2026-129448 was not listed in the KEV catalog. That status does not reduce the urgency created by the NVD’s statement that the vulnerability is actively exploited.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Last verified: 2026-11-17

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.