The Apache Software Foundation has published a new vulnerability record for Apache Roller, its Java blogging server, and the record includes a sentence that changes how quickly administrators need to act: "This issue is being actively exploited."
The flaw is tracked as CVE-2026-129448. It has a CVSS 3.1 score of 9.8 out of 10, and an unauthenticated attacker anywhere on the network can trigger it. The ASF says it allows remote code execution through Roller's XML-RPC endpoint. Versions 4.0.0 through 6.1.4 are affected, and the fix is in Roller 6.1.6.
The record was published on November 17, 2026, by the ASF's security team ([email protected]). It also says this is not a newly discovered bug. According to the CNA text and The Hacker News's November 18 report, CVE-2026-129448 is the same vulnerability as CVE-2026-82384, a 9.8-rated flaw that was patched in September 2026 and listed only Apache Roller 6.1.5 as affected.
What went wrong in Roller
XML-RPC is an old remote-procedure-call protocol. Blog platforms have used it for years to let desktop editors and other tools post to a blog over HTTP. Roller serves it at the /roller-services/xmlrpc path.
The bug falls under CWE-502, deserialization of untrusted data. Serialization turns an in-memory object into data that can be sent over the wire. Deserialization turns that data back into a live object. If a server rebuilds objects from data an attacker controls, the attacker can sometimes make it construct objects whose side effects run code. That is how many of the worst Java vulnerabilities of the last decade worked.
The record pins down where Roller goes wrong. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. "Vendor extensions" are non-standard data types that some XML-RPC libraries can be configured to accept, in addition to the basic strings, integers and structs the protocol defines. Because Roller handles those types before it checks who is asking, the dangerous step happens before any login. That is why the CVSS vector reads AV:N/AC:L/PR:N/UI:N: network-reachable, low complexity, no privileges and no user interaction needed.
What Apache has and hasn't said
The advisory is short. The ASF has confirmed exploitation but, as The Hacker News noted, it did not share details on how the flaw is being exploited or who is being targeted. The record does not say how many installations have been affected, and it names no victims or threat actor. ZeroDayFeed has no information beyond what the advisory and the reporting say.
The Hacker News credits a researcher identified as n0mi1k with finding the flaw and Matt Raible with reporting it.
As of November 18, CVE-2026-129448 does not appear in CISA's Known Exploited Vulnerabilities (KEV) catalog. We checked the catalog's JSON feed, and neither this CVE nor CVE-2026-82384 is listed. Federal agencies and contractors who use KEV to set patch deadlines should not read that as a sign the bug is low priority. The vendor's own record already confirms exploitation, whether or not CISA has added it yet.
Why a second CVE for the same bug matters
Usually, duplicate CVE records are just paperwork. This one isn't. The original CVE-2026-82384 was patched in September and listed only Roller 6.1.5 as affected. Apache has now issued a new identifier for the same vulnerability, with a much wider affected range of 4.0.0 through 6.1.4 and a fix that requires 6.1.6. Administrators who patched or reviewed their systems in September should not assume they are covered. Your scanner may only know the old CVE number, and the old record described a much narrower set of versions. Check what version is actually running.
The wide range also matters. It reaches back to Roller 4.0.0, so installations that have sat untouched for years are in scope. Those are often the servers nobody is watching.
What It Means for Defenders
Who is affected: Anyone running Apache Roller 4.0.0 through 6.1.4 with the XML-RPC servlet reachable. Roller is a niche platform, but a remote code execution foothold on any internet-facing blog server is valuable to an attacker, and this one needs no credentials.
What to do now:
- Upgrade to Roller 6.1.6 or later. This is the fix the ASF names in both the NVD and CVE.org records. If you updated in September for CVE-2026-82384, confirm you are on 6.1.6, not an earlier build.
- If you cannot upgrade right away, apply Apache's workaround at the deployment level. The ASF gives two options. You can set the
enabledForExtensionsparameter to "false" inWEB-INF/web.xml, or you can remove the/roller-services/xmlrpcservlet mapping. Restart Roller after either change. If you don't use XML-RPC clients, removing the mapping takes the endpoint out of play entirely. - Do not rely on the admin UI toggle. The advisory says plainly that disabling XML-RPC in Roller's administration interface is not enough, because older versions deserialize the request before checking that setting.
- Restrict exposure at the edge. Few sites still need public XML-RPC. Blocking
/roller-services/xmlrpcat a reverse proxy or WAF limits who can reach the endpoint while you patch. Treat this as an extra layer on top of the workaround above, not a replacement for it. - Consider exposed, unpatched hosts potentially compromised. Apache confirms in-the-wild exploitation but its record includes no indicators of compromise. If a vulnerable Roller instance was reachable from the internet, review its web and application logs for unusual POST traffic to the XML-RPC path. Look for unexpected child processes or new files under the application server, and check outbound connections from the host. Rotate credentials the Roller server could access, including database passwords, mail credentials and any API keys in its configuration. If you find signs of tampering, rebuild the server rather than cleaning it.
- Update your asset inventory and scanner rules. Make sure your vulnerability tooling recognizes both CVE-2026-129448 and CVE-2026-82384. Small Java applications deployed years ago often slip off the list.
For CMMC and other compliance-driven shops, keep a record of the version check, the upgrade or workaround, and any log review. A vendor-confirmed actively exploited flaw with a 9.8 score is likely to draw attention from assessors whether or not it reaches KEV.