Apache Roller CVE-2026-129448 (CVSS 9.8) Exploited: Unauthenticated XML-RPC Deserialization Gives Remote Code Execution on Every Release From 4.0.0, Not Just 6.1.5 — Upgrade to 6.1.7

Cyber · 2026-11-19 · By H.A

Apache Roller CVE-2026-129448 (CVSS 9.8) Exploited: Unauthenticated XML-RPC Deserialization Gives Remote Code Execution on Every Release From 4.0.0, Not Just 6.1.5 — Upgrade to 6.1.7

The ASF confirms attackers are exploiting CVE-2026-129448, an unauthenticated XML-RPC deserialization flaw that the September advisory under-reported, which lets anyone run code on Apache Roller 4.0.0 through 6.1.5 even when XML-RPC is switched off.

The Apache Software Foundation has confirmed that attackers are exploiting a critical flaw in Apache Roller, the Java blogging platform. Anyone on the internet can use it to run code on the server without logging in. The bug, CVE-2026-129448 (CVSS 9.8), is not new. It is the same XML-RPC deserialization bug the project fixed in September as CVE-2026-82384. That first advisory listed only Roller 6.1.5 as affected, so admins running older 4.x, 5.x and 6.0.x installs may have assumed they were safe. They were not, and attackers are now going after them.

What Happened

The ASF published the new advisory at 15:02 Mauritius time (11:02 UTC) on 17 November 2026. It says Roller versions 4.0.0 through 6.1.4 can be hit by an unauthenticated remote code execution attack. It also states plainly: "This issue is being actively exploited."

The new record corrects the earlier one. CVE-2026-82384 was published at 00:12 Mauritius time on 26 September (20:12 UTC on 25 September). It described the same root cause but named only Roller 6.1.5. In practice, every Roller release from 4.0.0 onward accepted the dangerous input. The September record left out roughly a decade of releases.

The vulnerability was found by a researcher credited as n0mi1k. Matt Raible is credited as the reporter of the new record. The ASF has not said who is behind the attacks, what they install, or how many servers have been hit.

Technical Details

Roller exposes an XML-RPC endpoint at /roller-services/xmlrpc. It serves the old Blogger and MetaWeblog publishing APIs that desktop blogging clients used. The servlet behind it is built on the Apache XML-RPC library, which supports optional "vendor extension" data types. One of these lets a request carry a serialized Java object. If extensions are enabled, the library turns those bytes back into a live Java object while it is still parsing the request.

According to the advisory, two design choices combined to make this exploitable:

The result is classic Java deserialization (CWE-502). An attacker sends one crafted POST request carrying a serialized object chain ("gadget chain") built from classes on Roller's classpath. Deserializing it runs code as the account that runs the servlet container, usually Tomcat. No account, no user interaction and no special configuration are needed. The CVSS vector is AV:N/AC:L/PR:N/UI:N.

The fix, merged in pull request 171 on 6 September (20:43 UTC on 5 September), does two things. It disables the vendor extension types, and it closes the endpoint when the webservices.enableXmlRpc setting is off, instead of relying on checks inside each handler.

Public Exploit Code

A public GitHub repository describing a proof of concept, scanner, exploit and test lab for CVE-2026-129448 appeared at 01:58 Mauritius time on 19 November (21:58 UTC on 18 November). Reef Sentinel has not tested it. Public tooling usually lowers the bar for opportunistic mass scanning, so any internet-facing Roller instance should be treated as a likely target from now on.

Who Is Affected

As of the CISA catalogue update at 23:17 Mauritius time on 18 November (19:17 UTC), the flaw was not listed in CISA's Known Exploited Vulnerabilities catalogue. CISA's enrichment data on the CVE record still marked exploitation as "none". The confirmation of attacks comes from the vendor, the ASF, not from US authorities.

Patch Status

Roller 6.1.6 (released 24 September 2026) is the minimum version that fixes this bug. Don't stop there, though. Roller 6.1.7, released on 11 November 2026, fixes 15 more CVEs. They include CVE-2026-123374, a separate deserialization flaw in update-ping responses, and CVE-2026-105153, an XML external entity bug in AtomPub parsing. Version 6.1.6 itself fixed 18 issues, including XXE, SSRF, CSRF bypass and a Velocity sandbox escape. Upgrade to 6.1.7. Release candidates for 6.1.8 and 7.0.0 are visible in the project's repository but have not been announced as releases.

What To Do Now

# Check whether extensions are enabled in the deployed Roller config
grep -n -A2 "enabledForExtensions" /path/to/tomcat/webapps/roller/WEB-INF/web.xml

# POST requests to the XML-RPC endpoint (most installs see almost none)
grep -E '"POST [^"]*/roller-services/xmlrpc' /var/log/nginx/access.log* /path/to/tomcat/logs/localhost_access_log* 2>/dev/null

# New or modified JSP/class files in the webapp since the advisory window
find /path/to/tomcat/webapps -type f \( -name '*.jsp' -o -name '*.class' -o -name '*.jar' \) -newermt '2026-09-01' -ls

# Unexpected child processes of the servlet container
ps -ef --forest | grep -A3 '[c]atalina'

Why It Matters

This case shows a quiet risk in vulnerability management: an advisory with an incomplete affected-version list. Many organisations triage by comparing their installed version with the CVE record. A September notice that named only 6.1.5 told anyone on 5.2 or 6.0 that they had nothing to do. It took about seven weeks, and attacks in the wild, before the record was widened to cover a decade of releases.

It is also another reminder that Java deserialization keeps coming back. Old protocol endpoints that nobody uses, like XML-RPC on a blog engine, often stay mapped, reachable and processing input long after the feature is "off". If a service doesn't need an endpoint, remove it at the servlet mapping and at the proxy, not just with a checkbox.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.