Apache Roller Vulnerability CVE-2026-129448: Apache Confirms Active Exploitation, and What Is Confirmed for the vCenter, Expressway and SAP Flaws Reported With It
Apache confirms CVE-2026-129448 in Apache Roller is being actively exploited. Upgrade to 6.1.6 or later. Here is what the vendors confirm, and what they do not, for the vCenter, Expressway and SAP flaws reported alongside it.
Where Worldwide
On this page 9 sections
Apache has confirmed that attackers are already using CVE-2026-129448, a flaw in its Apache Roller blog software. If your company runs Roller from version 4.0.0 up to (but not including) 6.1.5, upgrade to 6.1.6 or later this week.
The Roller flaw is being reported alongside three others, in VMware vCenter, Cisco Expressway and SAP NetWeaver, and some coverage describes all four as under attack. The vendor pages we checked tell a more mixed story. This post separates what is confirmed from what is only claimed, and gives you an order to patch in.
Apache Roller, vCenter, Expressway and SAP: what is confirmed
| Product | CVE | Exploitation, per the primary source | Fix in our sources |
|---|---|---|---|
| Apache Roller | CVE-2026-129448 | Confirmed: Apache says it is being actively exploited | Upgrade to 6.1.6 or later |
| VMware vCenter | CVE-2026-123890 | Not confirmed in our sources | Broadcom advisory (fixed versions not in our sources) |
| Cisco Expressway | CVE-2026-76466 | Cisco not aware of malicious use, as of its advisory | Cisco advisory and our earlier post |
| SAP NetWeaver Enterprise Portal | CVE-2025-42884 | Not stated in the CVE record | SAP Note 3660969 |
In the sources we checked, Apache Roller is the only one of the four with a vendor statement that it is being exploited. That does not make the other three safe. It means the evidence is different for each one, so plan for each one separately.
What about the CISA list?
Some coverage says all four flaws were added to CISA's Known Exploited Vulnerabilities catalog. We have not confirmed that from CISA itself, so we are not stating it as fact. If you track that catalog for compliance, check each CVE id above in it directly before you report on it.
Apache Roller vulnerability CVE-2026-129448: what Apache says
Apache's security page for Roller puts it plainly: "This issue is being actively exploited."
Apache lists the affected versions as Apache Roller from 4.0.0 before 6.1.5. The fix is to upgrade to Roller 6.1.6 or later. According to Apache, the fixed release "disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled".
That wording shows the fix involves the way Roller handles XML-RPC. The sources we checked do not tell us:
- what an attacker can do once the flaw is exploited
- who is being attacked, or how many sites
- whether any setting works as a safe stopgap on an older version
A note on the version numbers
Apache's affected range stops before 6.1.5, but the fix it points to is 6.1.6 or later. If you are on 6.1.5, keep going. Version 6.1.6 or later is past both numbers, and it is the simplest instruction to give whoever looks after the server.
Is turning off XML-RPC enough?
We could not confirm that it is. In what we checked, Apache does not describe turning the XML-RPC feature off as a workaround. Treat the upgrade as the fix, not the setting.
VMware vCenter CVE-2026-123890: rated 9.8 Critical
Broadcom's advisory lists CVE-2026-123890 with a CVSSv3 score of 9.8, rated Critical. That is near the top of the scale.
The Broadcom text we confirmed does not say whether this flaw is being exploited, and our sources do not give the affected or fixed vCenter versions. Open the Broadcom advisory, find your vCenter version, and apply the fixed release it lists. A 9.8 on the console that runs your virtual servers is worth patching this week, even without confirmed attacks.
Cisco Expressway CVE-2026-76466: Cisco says no known attacks
We covered this flaw in detail in our Cisco Expressway CVE-2026-76466 post, including which release to install, so we will not repeat that here.
What matters for this roundup is this: Cisco's advisory lists CVE-2026-76466 as CWE-798, and Cisco said it was "not aware of any public announcements or malicious use of the vulnerability" as of the advisory. That does not match headlines calling it under attack. Keep in mind that Cisco's statement reflects the advisory, not today. Check the advisory again before you close the ticket.
SAP NetWeaver CVE-2025-42884: injection with no login
The CVE record says the flaw in SAP NetWeaver Enterprise Portal "allows an unauthenticated attacker to inject JNDI environment properties". The affected components it lists are EP-BASIS 7.50 and EP-RUNTIME 7.50.
The record gives the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. In plain terms, the flaw can be reached over the network, is not hard to use, and needs no login and no action from a user. It is rated low impact on confidentiality and integrity, and no impact on availability. That is a real flaw, but the vector does not back up calling it critical. The record we checked does not say it is being exploited.
The fix listed is SAP Note 3660969, released on SAP Security Patch Day.
What to do this week
| Priority | Product | Action | How to check |
|---|---|---|---|
| 1 | Apache Roller | Upgrade to 6.1.6 or later | Confirm the version on every Roller install, including old, test and staging sites |
| 2 | VMware vCenter | Apply the fixed release in Broadcom's advisory for CVE-2026-123890 | Compare your vCenter version against the advisory |
| 3 | SAP NetWeaver Enterprise Portal | Apply SAP Note 3660969 | Check whether EP-BASIS 7.50 or EP-RUNTIME 7.50 is in use and whether the note is applied |
| 4 | Cisco Expressway | Install the fixed release in Cisco's advisory | See our earlier post and check the exploitation status again |
Also this week:
- List every server running these products, including ones nobody has logged into for a year.
- If a Roller site on an affected version was open to the internet, have someone check it for signs of tampering after you upgrade. Apache confirms the flaw is being exploited.
- Do not swap a settings change in for the Roller upgrade.
- Write down who is responsible for patching each system. If the answer is nobody, read who is patching the software that runs your business.
Why this matters for a business website or network
Blog servers often get set up once for marketing and then forgotten. The blog sits on your domain and is open to the internet, and it is easy to leave off the patch list because it is not the main site. Now that Apache has confirmed exploitation, the risk is real for anyone running an affected version.
The other three flaws sit deeper in a company network, on systems that IT teams patch on a schedule. A Critical rating or an exploitation report can mean that schedule needs to move up. We wrote about the gap between having an update and installing it in Updated is not the same as patched. If your public site worries you more broadly, see your website is live: can anyone find it, and is it locked?.
Apache Roller vulnerability questions people are asking
Is the Apache Roller vulnerability being exploited?
Yes. Apache's security page says: "This issue is being actively exploited."
Which Apache Roller versions are affected by CVE-2026-129448?
Apache lists Apache Roller from 4.0.0 before 6.1.5. Upgrade to 6.1.6 or later.
Is there a workaround for CVE-2026-129448?
Not one we could confirm. Upgrading is the fix.
What does the Apache Roller exploit let attackers do?
The sources we checked do not say. They confirm only that the flaw is being exploited and that the fix changes how Roller handles XML-RPC requests.
Is VMware vCenter CVE-2026-123890 being exploited?
Our sources do not confirm that. Broadcom rates it 9.8, Critical, so patch it anyway.
Is Cisco Expressway CVE-2026-76466 under attack?
Cisco's advisory said Cisco was not aware of any public announcements or malicious use as of the advisory. Check the advisory again for updates.
How do I fix SAP NetWeaver CVE-2025-42884?
Apply SAP Note 3660969. The affected components are EP-BASIS 7.50 and EP-RUNTIME 7.50.
Did CISA add these four flaws to its exploited list?
Some coverage says so. We have not confirmed it from CISA, so check the catalog directly.
The bigger lesson
Headlines bundle flaws together because four flaws make one story. Each vendor's own page often says something different. Sort by what each vendor confirms, patch the flaw confirmed as exploited first, then work through the critical ratings, and check the advisories again as they update.
Need help keeping the software that runs your business patched? See security hardening or get a quote.
Get security alerts like this by email, with our free checklist, at security alerts.
Sources: Apache Roller security page; Cisco security advisory; Broadcom security advisory; CVE-2025-42884 record.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Linux KVM Vulnerability CVE-2026-99312: AMD Hosts With Nested Virtualization Affected, What Is Confirmed and How to Check Yours
A Linux kernel flaw in the KVM hypervisor, CVE-2026-99312, affects hosts with AMD processors and nested virtua...
PHP Critical Vulnerability: Seven RCE Flaws Fixed in PHP 8.5.13 and 8.6.0, Which Version to Install for Your Branch and Who Is Exposed
PHP's 19 November 2026 security releases fix seven critical remote code execution flaws. Here is which version...
PHP Session Vulnerability: CVE-2026-126714 and CVE-2026-115560 Can Lead to Remote Code Execution, Fixed in PHP 8.5.13, and What to Check This Week
PHP has fixed two session flaws, CVE-2026-126714 and CVE-2026-115560, that can lead to remote code execution....