CVEs / CVE-2026-129448
CVE-2026-129448: Apache Roller Deserialization of Untrusted Data Vulnerability
- Known exploited in the CISA KEV catalog since 20 Nov 2026
- critical 9.8 CVSS 3.1 (from the CNA)
- EPSS 1.19% chance of exploitation in the next 30 days, higher than 68% of CVEs (20 Nov 2026)
- Last changed at its sources
Are you affected? Check your servers with Stackurity: it lists the software on each server and the vulnerabilities to fix first.
Check your servers with Stackurity Already using Stackurity? Search for CVE-2026-129448
Summary
Apache Roller contains a deserialization of untrusted data vulnerability that allows an unauthenticated remote attacker to execute arbitrary code via the XML-RPC endpoint, which accepts and deserializes vendor extension types before authentication. This CVE covers the same underlying vulnerability as CVE-2026-82384 but applies to a broader range of affected versions.
Description
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 XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited. Users are recommended to upgrade 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. 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.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache Roller | from 4.0.0, before 6.1.5 | 6.1.5 |
Exploitation
| In CISA KEV since | 20 Nov 2026 |
|---|---|
| Due date for US federal agencies | 23 Nov 2026 |
| Used in ransomware campaigns | Unknown |
| Required action | Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. |
Severity
| CVSS 3.1 | 9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HScored by the CNA ([email protected]) |
|---|---|
| Weakness | CWE-502 |
On the Stackurity blog
References
- CVE-2026-129448 on NVD
- CVE-2026-129448 in the CISA KEV catalog
- https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9 (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (cited by CISA)
- CVE-2026-129448 on OSV
- https://github.com/apache/roller/pull/171 Issue Tracking, Patch
- https://lists.apache.org/thread.html/lnz4s26tv6hdo03wngtdbpfj4hg4gtds Mailing List, Vendor Advisory
- https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9 Mailing List, Not Applicable
- https://www.cve.org/CVERecord?id=CVE-2026-82384 Third Party Advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-129448 Third Party Advisory, US Government Resource
Sources
Exploitation status from the CISA Known Exploited Vulnerabilities catalog. EPSS scores from FIRST. Descriptions, severity and references from the National Vulnerability Database. Open-source package versions from OSV (CC-BY 4.0). Text is shown as each source states it; Stackurity does not edit it. Check the vendor's advisory before acting.
This product uses data from the NVD API but is not endorsed or certified by the NVD.