PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-82384 – Unauthenticated Remote Code Execution via XML-RPC Deserialization – Apache Roller 6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82384 is a critical unauthenticated deserialization vulnerability (CWE-502) in Apache Roller’s XML-RPC endpoint that can lead to remote code execution. The flaw affects Apache Roller 6.1.5 and carries a CVSS v3.1 base score of 9.8 (Critical). Because the vulnerable code path is processed before any authentication check, a remote attacker with no credentials can trigger deserialization of attacker-controlled data.

Technical details

  • Root cause: Roller’s XmlRpcServlet is configured with enabledForExtensions=true, causing the underlying Apache ws-xmlrpc library to accept vendor extension value types — including ex:serializable, a base64-encoded Java serialized object.
  • Trigger condition: This vendor-extension parsing occurs during initial HTTP request handling, before the Blogger/MetaWeblog authentication checks are evaluated, allowing a crafted request to reach the deserialization logic without valid credentials.
  • Persistence of exposure: The XML-RPC servlet is mapped unconditionally in web.xml, so the vulnerable parsing path remains reachable even when the global webservices.enableXmlRpc setting is disabled — no non-default configuration is required for exploitation.
  • Attack vector: Network-based; an attacker sends a crafted XML-RPC POST request (containing an ex:serializable element with a malicious serialized Java object) to the Roller XML-RPC endpoint.
  • Impact: Successful exploitation of a suitable deserialization gadget chain can result in arbitrary code execution in the context of the Roller application/JVM process, with complete loss of confidentiality, integrity, and availability.
  • A public proof-of-concept and exploitation tooling for this vulnerability have been published, increasing the likelihood of opportunistic scanning and exploitation.

Affected software

  • Apache Roller 6.1.5

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Roller 6.1.6 or later, which disables the vendor extension types on the XML-RPC servlet and rejects requests when the XML-RPC feature is globally disabled.
  • If immediate patching is not possible:
    • Block external network access to the XML-RPC servlet path on internet-facing Roller instances.
    • Deploy a Web Application Firewall (WAF) rule to inspect and drop XML-RPC requests containing serialization markers such as ex:serializable.
    • Monitor server logs for unusual or malformed requests targeting the XML-RPC endpoint to detect potential exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge