Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Apache Roller XML-RPC RCE (CVE-2026-129448 / CVE-2026-82384)

CVE-2026-129448 is an Apache Roller XML-RPC deserialization flaw also identified as CVE-2026-82384.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
4 min read
CVE ID
CVE-2026-129448
Vendor
Apache Software Foundation
Affected Product
Apache Roller
Exploitation
Yes
Published
2026-11-17

Apache says an unauthenticated remote attacker can execute arbitrary code, and the two identifiers describe the same vulnerability.Apache rates it Critical at CVSS 3.1 9.8 and says exploitation is active. Teams responsible for exposed Roller servers should prioritize the 6.1.6 upgrade in their vulnerability intelligence platform and verify the running version afterward.

What it allows

How Does CVE-2026-129448 Reach Code Execution?

Apache says Roller accepts XML-RPC extension types and deserializes them while parsing a request, before authentication. An unauthenticated caller can therefore reach unsafe deserialization, which can lead to remote code execution.

The XML-RPC servlet is mapped without a special configuration in the affected release. Apache says turning off XML-RPC in the administration interface is insufficient because parsing happens before that setting is checked. We map this exposure to MITRE ATT&CK T1190, Exploit Public-Facing Application; this is our defensive classification, not Apache's attribution of an attacker.

Is CVE-2026-129448 Being Exploited?

Yes. Apache's 17 November CNA record says this same vulnerability is being actively exploited. The announcement does not identify a campaign, a victim, or an exploitation start date, so this profile does not infer any of those details.

Brandefense Blackhole recorded one dark-chat match for CVE-2026-129448 and four for CVE-2026-82384 from 19 August to 17 November 2026. These are separate identifier searches that may overlap; their counts do not establish incidents or add up to unique posts.

A public GitHub repository search on 17 November found two repositories named for CVE-2026-82384. One repository's description labels itself a proof of concept; we have not verified its code or treated that claim as evidence of exploitation.

What Should Defenders Investigate?

Inventory internet-reachable Roller installations and establish their running versions before prioritizing remediation. Our suggested review is to examine application, proxy, and host logs around XML-RPC handling for unusual requests and unexpected process activity, then investigate any findings through the incident process.

Prioritize exposed installations because Apache reports unauthenticated access and active exploitation. Use the vulnerability intelligence record to keep the two CVE names attached to one remediation decision.

Who is affected

Which Roller Versions Are Affected by CVE-2026-129448 and CVE-2026-82384?

Apache lists Roller 4.0.0 through 6.1.4 under CVE-2026-129448 and Roller 6.1.5 under CVE-2026-82384. The 17 November record explicitly says these are the same flaw, so the combined affected range is 4.0.0 through 6.1.5.

The flaw can be reached without a nondefault XML-RPC configuration, according to the 6.1.5 notice. Even when XML-RPC is disabled in the administration interface, affected versions parse the request before checking that setting. Verify the deployed Roller build and XML-RPC exposure rather than relying on the interface toggle.

How Do Teams Fix and Verify the Issue?

Upgrade affected installations to Apache Roller 6.1.6 or later. Apache says that release disables the extension types and rejects XML-RPC requests when the feature is disabled. After rollout, check the version actually running on each server and confirm normal application behavior.

If immediate upgrading is impossible, Apache advises setting enabledForExtensions to false in the Roller web configuration or removing the XML-RPC servlet mapping, followed by a restart. Confirm the configuration is active after restart and schedule the 6.1.6 upgrade; the administration interface toggle alone does not mitigate the flaw.

Record the running-version check and interim setting in the patch management process. Review the affected period's relevant logs as an investigation step, not as proof that every exposed server was compromised.

Timeline

  1. 2026-09-25

    Apache disclosed CVE-2026-82384 for Roller 6.1.5 and recommended 6.1.6.

  2. 2026-11-13

    The saved CISA KEV catalog version 2026.11.13 contained neither identifier; this snapshot predates Apache's later notice.

  3. 2026-11-17

    Apache published CVE-2026-129448 for Roller 4.0.0 through 6.1.4, identified it as the same flaw as CVE-2026-82384, and reported active exploitation.

What to do

  1. Inventory exposed Roller servers

    Find Apache Roller installations and record the version actually running. Treat 4.0.0 through 6.1.5 as one affected range across the two CVE identifiers; prioritize internet-reachable servers.

  2. Upgrade and verify

    Deploy Apache Roller 6.1.6 or later. Restart or redeploy as needed, verify the running version on each server, and confirm normal application behavior.

  3. Apply Apache's interim setting if upgrade is delayed

    Set enabledForExtensions to false in the Roller web configuration or remove the XML-RPC servlet mapping, then restart. Verify the active setting; the administration interface toggle alone is insufficient.

  4. Review relevant activity

    As a Brandefense investigation step, review application, proxy, and host logs from affected servers for unusual XML-RPC handling and unexpected process activity. Investigate findings without assuming compromise from version alone.

What Brandefense can do

Frequently Asked Questions

Are CVE-2026-129448 and CVE-2026-82384 separate Apache Roller flaws?

No. Apache says CVE-2026-129448 covers 4.0.0 through 6.1.4 and is the same vulnerability as CVE-2026-82384, which covers 6.1.5.

Which Apache Roller version fixes both CVE-2026-129448 and CVE-2026-82384?

Apache recommends Roller 6.1.6 or later for the shared flaw. Verify the version actually running after the upgrade.

Does disabling XML-RPC in Roller administration remove this exposure?

No. Apache says affected versions deserialize the request before checking the administration setting. Upgrade or use Apache's temporary web configuration or servlet-mapping mitigation, then restart.

What confirms exploitation of CVE-2026-129448?

Apache's 17 November CNA record explicitly reports active exploitation of the same flaw. It does not give a campaign, victim, or start date.

Sources

  1. Apache Roller CVE-2026-129448 CNA RecordApache Software Foundation via CVE Program
  2. Apache Roller CVE-2026-82384 CNA RecordApache Software Foundation via CVE Program
  3. Apache Roller CVE-2026-129448 AdvisoryApache Software Foundation
  4. Apache Roller CVE-2026-82384 AdvisoryApache Software Foundation
  5. Exploit Public-Facing Application T1190MITRE ATT&CK
  6. Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →