Apache Roller’s Exploited Flaw Is Not Fixed by Switching Off XML-RPC, and SAP’s Medium-Rated Portal Bug Joins CISA’s Monday List
CISA has added Apache Roller, SAP NetWeaver Enterprise Portal, Cisco Expressway and VMware vCenter flaws to its exploited list, all due Monday. Apache says its own admin-screen switch does not protect Roller; SAP rated its flaw medium.

CISA added four exploited flaws to its Known Exploited Vulnerabilities catalogue on Friday 20 November, and gave US federal agencies until Monday 23 November to deal with all of them. Two are in products we have already covered, Cisco Expressway and VMware vCenter. The other two are less well known and more awkward than they look: an unauthenticated code-execution flaw in Apache Roller, where the obvious workaround does not work, and a flaw in SAP NetWeaver Enterprise Portal that SAP rated only medium a year ago and that CISA now says is being used in attacks.
The Monday date is a US federal rule and not a UK obligation. We are using it here as a prompt: a Friday evening list with a Monday date is a reasonable way to decide what gets looked at first this weekend.
#Apache Roller: switching off XML-RPC in the admin screen is not enough
Apache Roller is an open-source blogging server written in Java. The flaw, CVE-2026-129448, is scored 9.8 out of 10, and the Apache Software Foundation’s own text in the CVE record says it “is being actively exploited”. According to that record, versions 4.0.0 through 6.1.4 contain a deserialisation flaw in the XML-RPC endpoint: the endpoint accepts “vendor extension types” and unpacks them before it has checked who is asking. An attacker needs no account, only network access to the endpoint, and can run arbitrary code on the server.
The detail that matters most to anyone running Roller is in the workaround Apache gives. Apache says users who cannot upgrade straight away should set “enabledForExtensions” to “false” in WEB-INF/web.xml, or remove the “/roller-services/xmlrpc” servlet mapping, and then restart Roller. It adds that disabling XML-RPC in the administration screen is not enough, because older versions deserialise the request before they check that setting. We would expect plenty of administrators to reach for that switch first, since it is the obvious one, and Apache is saying it leaves the hole open.
The fix is Roller 6.1.6 or later, which Apache says disables the extension types and refuses XML-RPC requests when XML-RPC is turned off. There is also a version wrinkle. The record for this CVE gives the affected range as 4.0.0 through 6.1.4, but it says it describes the same flaw as an earlier identifier, CVE-2026-82384, which listed only 6.1.5 as affected. Taken together, that means 6.1.5 should not be treated as safe, and our reading is that anything below 6.1.6 should be treated as exposed until you have confirmed otherwise. Security Affairs, which reported the flaw on 18 November, repeats the 4.0.0 to 6.1.4 range and the 9.8 score.
Who is affected? Anyone running Roller; we do not know how many organisations that is. If it is not you, you can stop reading this section. If it is, the first job is not to patch but to find out whether the server was reached. CISA’s catalogue entry carries a “forensic triage” flag set to “Yes”, and lists known ransomware use as “Unknown”. As we read it, the flag means a system that was exposed should be examined and not just updated. Because the vulnerable code runs before authentication, we would not read a failed login in a log as a failed attack: look instead for any request to the XML-RPC path from addresses you do not recognise, and for new processes or files on the host that you cannot explain.
#SAP NetWeaver Enterprise Portal: a medium score, and an active flag
The SAP flaw, CVE-2025-42884, is the oldest item on the list. SAP’s CVE record was published on 11 November 2025, so a fix has been available for a year. The record describes a JNDI injection flaw in SAP NetWeaver Enterprise Portal: an unauthenticated attacker can inject JNDI environment properties, or pass in a URL used during a JNDI lookup, and so reach “an unintended JNDI provider”. JNDI is Java’s directory lookup mechanism, and the risk in plain terms is that the server can be steered into asking somewhere the attacker chooses. SAP says this could lead to disclosure or modification of information about the server, with no effect on availability. It rates the flaw 6.5 out of 10, which is medium. The affected components it lists are EP-BASIS 7.50 and EP-RUNTIME 7.50.
What has changed is the evidence of use. CISA’s entry for the flaw was added on 20 November, and the CISA enrichment attached to the CVE record, time-stamped 18:42 UTC that day, marks exploitation as “active” and the flaw as “automatable”. CISA’s catalogue also carries the 23 November due date, with the forensic triage flag set to “No” for this one, unlike the others. Nobody we have read has said who is exploiting it, against whom, or how, and CISA’s entry does not either. We are not going to guess.
SAP’s fix is described in SAP Note 3660969, which the CVE record points to. The note sits behind SAP’s support login and we could not read it, so we cannot tell you which support package levels contain the fix. Your SAP basis team can, and this is the question to put to them on Monday morning: is Enterprise Portal on 7.50 here, is it reachable from the internet or from a supplier network, and is Note 3660969 applied?
Our view is that the medium score misled. A score of 6.5 describes what the flaw can do once reached, and the weakness here is that an unauthenticated attacker can reach it over the network with low complexity, which fits CISA’s “automatable” label. Our reading is that information disclosure on an enterprise portal is rarely the end of an intrusion: it is a way for an attacker to learn what the server is connected to.
#The two you may already have seen
The Cisco entry is CVE-2026-76466, a hard-coded credentials flaw in Cisco Expressway Series. CISA describes it as letting an unauthenticated remote attacker with persistent cookies and network access run commands as root on a clustered device through the database service. The VMware entry is CVE-2026-123890, the vCenter authentication bypass. Both carry the same 23 November due date and both have the forensic triage flag set to “Yes”, and for both the known ransomware use field reads “Unknown”. We covered them earlier: the Cisco Expressway story has the fixed release and the migration problem for older versions, and the vCenter story now includes what the listing changes and a hunt list that goes back to September. Neither needs repeating here.
#What to do before Monday
- Work out which of the four you run. Most organisations will have one or two, and some will have none, in which case there is nothing to do.
- For vCenter and Expressway, follow the earlier stories: patch, and check whether the server was reached before you did.
- For Roller, upgrade to 6.1.6 or later. If you cannot do that today, apply Apache’s workaround in web.xml and restart, and do not rely on the setting in the admin screen.
- For SAP, ask your basis team the three questions above, and ask for the answer in writing, because the person who knows the 7.50 portal is often not the person who owns the firewall rule.
- For anything that was exposed and unpatched, treat it as possibly compromised. The forensic triage flags on three of the four entries point the same way.
#Why we read the flags and not the scores
Two of these four have scores that would not set off an alarm in a patch queue sorted by severity: the SAP flaw at 6.5, and a Roller bug that most teams would never have heard of. Both appear on the list because someone has seen them used. That is the pattern we keep coming back to in these stories. In our view, a patch queue sorted by score alone will put the SAP flaw behind dozens of items that nobody is known to be exploiting, because the score describes the damage and not the odds of an attack.
We expect more of this sort of listing, not less: older flaws in enterprise Java products reaching the catalogue long after the fix, as the SAP entry has. Our guess, and it is only a guess, is that attackers expect year-old patches to be missing in some places. What would prove us wrong is a run of weeks in which every addition is a fresh zero-day. We will update this story if any of the four vendors changes its advice or if someone reports who is behind the attacks.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01CISA Known Exploited Vulnerabilities catalogue, release of 20 November 2026cisa.gov
- 02CVE record for CVE-2026-129448 (Apache Software Foundation)cveawg.mitre.org
- 03CVE record for CVE-2025-42884 (SAP), with CISA's enrichmentcveawg.mitre.org
- 04Security Affairs, Apache Roller RCE flaw CVE-2026-129448 under active attacksecurityaffairs.com
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All news
Artificial IntelligenceMicrosoft Will Switch Claude On in Copilot for Tenants That Have Not Chosen, From 9 December

Artificial IntelligenceGoogle Now Keeps Gemini Chats for About Two Months Even With History Off, Up From 72 Hours

Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.
Comments
Add a thoughtful note on Apache Roller’s Exploited Flaw Is Not Fixed by Switching Off XML-RPC, and SAP’s Medium-Rated Portal Bug Joins CISA’s Monday List. Comments are checked for spam and held for moderation before appearing.