Skip to main content
All vulnerabilities
CVE-2026-129448 CVSS 9.8

Apache Roller Deserialization of Untrusted Data Vulnerability

Apache — Roller

Published to NVD
17 November 2026
Disclosure to KEV listing
3 days
EPSS (30-day exploitation probability)
1.2% · 68.7th percentile · 20 November 2026
Added to KEV catalog
20 November 2026
Federal remediation due date
23 November 2026
Weakness classification (CWE)
CWE-502

Is CVE-2026-129448 actively exploited?

Yes. CISA added CVE-2026-129448 to its Known Exploited Vulnerabilities catalog on 20 November 2026, which means there is evidence it has been exploited in the wild. FIRST's EPSS model estimates a 1.2% probability of exploitation activity in the next 30 days, placing it in the 68.7th percentile of all scored CVEs.

How severe is CVE-2026-129448?

CVE-2026-129448 has a CVSS base score of 9.8 out of 10, rated Critical. Its CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The score measures technical severity; active exploitation, shown by the KEV listing, is the stronger reason to act quickly.

Which versions are affected by CVE-2026-129448?

NVD lists these affected versions for CVE-2026-129448: Apache Roller: from 4.0 up to (not including) 6.1.5.

How do I fix CVE-2026-129448?

CISA's required action for CVE-2026-129448 is: 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. The vendor advisory and patch links on this page point to the vendor's own fix guidance. US federal agencies must remediate it by 23 November 2026; treat that as an outside deadline, not a target.

Affected versions (NVD)

  • Apache Roller: from 4.0 up to (not including) 6.1.5

Version ranges as published in NVD's CPE configurations. Confirm against the vendor advisory before relying on them.

AI Breakdown

What it is

Apache Roller contains a critical security flaw in its XML-RPC interface affecting versions 4.0.0 through 6.1.4. An unauthenticated remote attacker can exploit this by sending crafted data that the server deserializes before verifying user credentials. This flaw allows attackers to execute arbitrary code directly on the host system without needing a login.

Why it matters

With a critical CVSS score of 9.8, this flaw gives remote attackers full control of the hosting server and is confirmed to be actively exploited in the wild. While specific ransomware campaign use is currently unknown, the threat of immediate unauthorized takeover makes this an urgent risk for any exposed instance.

Recommended action

Upgrade immediately to Apache Roller version 6.1.6 or later, which disables vulnerable extension types and rejects unauthorized XML-RPC requests. If an immediate upgrade is not possible, mitigate the threat by setting enabledForExtensions to false in WEB-INF/web.xml or removing the /roller-services/xmlrpc servlet mapping and restarting Roller, as disabling the feature in the administration UI is insufficient. Organizations unable to apply vendor mitigations should follow CISA BOD 26-04 guidance and discontinue product use.

AI-generated from CISA and NVD data — treat as a starting point, not a substitute for your own risk assessment.

CISA Description

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.

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.

Notes

https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-129448

NVD Technical 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.

Confirm Your Exposure

Is this vulnerability present in your environment?

CRS delivers independent VAPT assessments that identify exactly which known-exploited vulnerabilities exist in your network, applications, and infrastructure.

Explore VAPT Services