Skip to main content
Menu
CVEs

CVE

Apache Roller unauthenticated code execution in XML-RPC endpoint

Affects Apache Roller from 4.0.0 before 6.1.5 when the XML-RPC endpoint accepts vendor extension types, as the default setup did before the fix. CVSS scores it 9.8 (critical). Fixed in 6.1.5.

CVE-2026-129448EUVD-2026-126955

Written by a model from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · apache rates this critical

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 6.1.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 6.1.5.

Published
Last modified
Reference
Last checked
30/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

Apache Roller has a deserialization flaw in its XML-RPC endpoint that lets a remote attacker run arbitrary code on the server without logging in. The endpoint deserializes vendor extension types before it checks the requester's identity.

Original 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.

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 6.1.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129448 (Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129448 (entry last updated 2026-11-17):
Affected:
- Apache Software Foundation Apache Roller: from 4.0.0, fixed in 6.1.5
Fixed versions: 6.1.5.
Conditions (all must be true for the bug to be hit):
- XML-RPC endpoint of Apache Roller with vendor extension types enabled (default servlet setup before the fix) (source: https://github.com/apache/roller/pull/171)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129448 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129448 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9
- https://lists.apache.org/thread.html/lnz4s26tv6hdo03wngtdbpfj4hg4gtds
- https://github.com/apache/roller/pull/171
- https://www.cve.org/CVERecord?id=CVE-2026-82384
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129448
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129448"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • Apache Software Foundation Apache Roller

    From 4.0.0 · fixed in 6.1.5

Evidence 6

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Advisory
  2. Advisory

CVE record · 3

Establishes: The identifier and description.

  1. Record
  2. Record
  3. Link

Other links · 1

  1. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129448

Is CVE-2026-129448 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The XML-RPC endpoint of Apache Roller performs deserialization without requiring authentication, which is the flaw this advisory describes.Source: github.com

Which versions are affected by CVE-2026-129448?

Apache Roller: from 4.0.0 before 6.1.5.Source: cve.now feed data

Am I affected, and how do I check?

The listed range is Apache Roller 4.0.0 up to but not including 6.1.5. The affected setup is an XML-RPC servlet configured to accept the library's non-standard vendor extension types, which was the default before the fix. To check, look at the Roller version and whether the XML-RPC servlet accepts vendor extension types in its configuration.Source: github.com

How do I fix CVE-2026-129448?

Upgrade to Apache Roller 6.1.5 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs