CVERadar

CVE-2026-129448: Apache Roller flaw exploited in the wild, what we know

CVE REPORT · EXPLOITED IN THE WILDCVE-2026-129448Apache RollerCRITICALCVSS 9.8cveradar.org

CVE-2026-129448 affects Apache Roller; exploited in the wild. What happened, who is affected, how far exploitation has gone and where the patch stands.

CVE-2026-129448 at a glance

CVE-2026-129448 is a critical-severity Deserialization vulnerability in Apache Roller, with a CVSS 3.1 base score of 9.8. NVD published it on 2026-11-17 and classifies the weakness as CWE-502. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-20; the federal remediation due date is 2026-11-23. Public exploit code: 2 public GitHub proof-of-concept repositories from 2 accounts, with the earliest exploit evidence dated 2026-11-18. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 1.19% (percentile 68.7, scored 2026-11-20). NVD configuration data lists a fixed release for 1 product, for example apache roller 6.1.5. CVERadar maps 3 MITRE ATT&CK techniques across Initial Access and Execution, inferred from the CWE and the description. Its CVERadar threat level is 64/100.

Full CVE-2026-129448 record: exploitation evidence, ATT&CK chain and every source.

What it is

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.

  • Severity: CRITICAL (CVSS 3.1 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
  • Weakness: CWE-502.
  • NVD published 2026-11-17, status Analyzed.

Who's affected

Anyone running Apache Roller in the version ranges below. Internet-facing instances are the priority.

  • apache roller: from 4.0 up to (not including) 6.1.5.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

Exploitation status

  • Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-20; federal remediation due date 2026-11-23.
  • Public proof-of-concept code: 2 GitHub repositories from 2 accounts, the first on 2026-11-18.
Verify before running: public exploit and proof-of-concept code can be fake or carry malware. Only run it in an isolated lab, after reading the code.

What this means for a small business

CISA added CVE-2026-129448 to its Known Exploited Vulnerabilities catalog on 2026-11-20. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs Apache Roller, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-23 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Update to a fixed release: apache roller 6.1.5 or later. These versions come from NVD's configuration data, so confirm them against the advisory from Apache.
  • If you cannot patch yet. Follow CISA's 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.
  • Check your exposure. Find out whether Apache Roller can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
  • When to call IT support. Call your IT support provider now if you run Apache Roller and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

Risk

  • EPSS (probability of exploitation activity in the next 30 days): 1.19%, higher than 69% of all scored CVEs (as of 2026-11-20).
  • CVERadar threat level: 64/100 (see methodology).
  • Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1059 Command and Scripting Interpreter (inferred); T1203 Exploitation for Client Execution (inferred).

Remediation steps

  1. Find every instance. List where Apache Roller runs, including test, DR and forgotten internet-facing systems, and record the installed version.
  2. Upgrade to a fixed release. apache roller: 6.1.5 or later. Get the build from the vendor advisory.
  3. If you can't patch today, follow CISA's 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.
  4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (6.1.5 or later). Re-scan from outside if the service is exposed.
  5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
  6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

  • T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Roller (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-11-17.
  • T1059 Command and Scripting Interpreter: Watch for the service process spawning shells or script interpreters.
  • T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.
Bash · T1059 hunt
# Child processes of web/service accounts (look for sh, bash, python, perl, curl, wget)
ps -eo pid,ppid,user,lstart,cmd --forest | grep -E "www-data|apache|nginx|tomcat" -A3

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

Sources

← Back to blog
Keep reading

Related articles

Track every exploited CVE

Full record for CVE-2026-129448, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.

Exploited in the wildHow we score