CISA adds Apache Roller and SAP NetWeaver to KEV; Roller has two CVE ids for one flaw, SAP's record is 374 days old
CISA's catalogue of 20 November 2026 lists Apache Roller CVE-2026-129448, which Apache's record says is the same flaw as CVE-2026-82384 published 50 days earlier, and SAP CVE-2025-42884, a Medium record 374 days old (derived). No saved page says who exploits either.
By Parminder Kumar Sharma · LinkedIn · · 19 min read
A Roller flaw with two ids and a SAP record 374 days old reached CISA's exploited list on one day (derived)
On Friday 20 November 2026 CISA added four entries to its Known Exploited Vulnerabilities (KEV) catalogue. The catalogue file this site read has catalogVersion 2026.11.20, was released at 17:48 UTC that day and holds 1,790 entries. Two of the four are the subject here: Apache Roller CVE-2026-129448 and SAP NetWeaver CVE-2025-42884. The other two, Broadcom VMware vCenter and Cisco Expressway, are in this site's briefings on vCenter and Cisco Expressway.
Roller. Apache's record for CVE-2026-129448 says it is "the same vulnerability as CVE-2026-82384", a record Apache published 50 days earlier (28 September to 17 November, derived) that named only Roller 6.1.5. Both name the same fix, 6.1.6, which the project's security page says was released on 24 September: 57 days before the KEV listing (derived). The two affected ranges do not overlap: 82384 names 6.1.5, and 129448 names 4.0.0 up to but not including 6.1.5. SAP. The record for CVE-2025-42884 was published on 11 November 2025 with a Medium score of 6.5 set by SAP. On the KEV date it was 374 days old (derived: 365 days to 11 November 2026, plus 9). CISA's part of the record rates exploitation active. SAP's own part of the record carries no update stamp after 11 November 2025 and does not mention exploitation.
What that does not establish. No page this site read says who exploits either flaw, how many systems were attacked, or since when. None counts how many Roller sites or SAP portals are reachable from the internet. None gives CISA's reason for listing them on 20 November. The age of a record is not a time anyone was exposed, and a fix that exists for 57 days is not a fix that was applied. SAP sells the product its record scores Medium, and its record is its own account of its own product. CISA's catalogue is a US government list. This site names no individual: the records and the pull request credit people, and none is named here.
Roller: one flaw, two ids, and two ranges that do not overlap
Apache published CVE-2026-82384 on 28 September 2026 at 07:47 UTC. It says Apache Roller 6.1.5 allows an unauthenticated remote attacker to cause deserialisation of attacker-controlled bytes, and that this "can lead to remote code execution". It adds that the servlet is "mapped unconditionally" and that no non-default configuration is required for this path. Its affected list holds one entry, 6.1.5, and its fix is "Apache Roller 6.1.6 or later". The record carries Apache's severity word Critical and a CVSS 3.1 base score of 9.8: network, low complexity, no privileges, no user interaction, high impact on confidentiality, integrity and availability. The vector is in the code block below.
On 17 November, 50 days later, Apache published CVE-2026-129448 (reserved on 14 November, a Saturday). Its record is titled "Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)" and says the flaw is in "versions 4.0.0 through 6.1.4". It states: "This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited." The score is the same 9.8 with the same vector. The fix is the same: 6.1.6 or later.
CISA's catalogue entry is for 129448. Its description ends: "This CVE covers the same underlying vulnerability as CVE-2026-82384 but applies to a broader range of affected versions." That sentence is true in the sense that 129448 covers many more releases than the single one 82384 names. It does not mean 129448 contains 82384's release. Read from the two records (derived), the ranges meet but do not overlap: 4.0.0 through 6.1.4 on one id and 6.1.5 on the other. Together they name 4.0.0 through 6.1.5.
The practical difference is in how a tool finds the flaw. A scanner or ticket feed that matches on 82384 alone sees a host running 6.1.5. One that matches on 129448 alone, the id CISA lists, sees 4.0.0 through 6.1.4 and not 6.1.5 (derived from the two ranges). This site does not know how any particular scanner behaves. It does know the two Apache records disagree on the affected list for a flaw they call one.
Which release each saved page names for the Roller XML-RPC flaw, as read on 21 November 2026
| Release | Named by | What the saved pages say |
|---|---|---|
| Before 4.0.0 | Neither id | Not stated. The 129448 range starts at 4.0.0 |
| 4.0.0 through 6.1.4 | CVE-2026-129448 | Affected. Fix 6.1.6 or later. Record text: being actively exploited |
| 6.1.5 | CVE-2026-82384 | Affected. Fix 6.1.6 or later. CISA-ADP rated Exploitation none on 28 September; the record was last updated on 29 September |
| 6.1.6 | Neither id (the fix) | Released 24 September. The project's page says each of its 18 advisories for 6.1.6 affects 6.1.5, and users of earlier versions should also upgrade |
| 6.1.7 | Neither id | Released 11 November, the latest on the page as saved. It fixes 15 further advisories. None is either id here |
What the exploitation sentence covers. The 129448 record says "This issue is being actively exploited", and says the issue is the same one 82384 describes. If it is one flaw, a host on 6.1.5 has the flaw that CISA lists (inference). The record does not say which releases were attacked, so the sentence does not tell a 6.1.5 operator that 6.1.5 was targeted. The Apache part of the 129448 record carries no update stamp later than its publication, 17 November at 11:03 UTC, so the sentence appears to have been in the record from the start (inference from the stamp; the saved JSON shows no edit history).
The dates to scale: 57 days from fix to listing, 50 days between the ids
Diagram 2 puts every date on one axis. The project's security page says Roller 6.1.6 was "released 24 September 2026", a Thursday, and lists CVE-2026-82384 as Critical, fixed in 6.1.6. The record followed on Monday 28 September, 4 days after the release (derived). The 129448 record came on Tuesday 17 November. CISA's catalogue added it on Friday 20 November, 3 days after the second record, 53 days after the first and 57 days after the fix (all derived).
The change was public before the advisory. The pull request page for the change both CVE records list as the patch shows it opened on 29 August 2026, approved, and merged on 5 September: 7 days later (derived). The release came 19 days after the merge, and the first record 23 days after it (derived). The page describes a change that turns off vendor extension types the project says Roller does not use and gates the endpoint on the setting webservices.enableXmlRpc. It does not use the word security and names no CVE id. The project's page says "Advisories are published when the fixed release is publicly available for download." A gap between merge and advisory is that policy at work, not a finding. It does mean the saved page shows the change as a public pull request from 29 August, before any record described the flaw.
Exploitation, date by date. The first record's CISA-ADP rating on 28 September was Exploitation: none. The second record, 17 November, says exploited. CISA-ADP's rating of it is stamped 18 November, 1 day after publication, with Automatable yes and Technical Impact total, and carries a date only, no time. No saved page says whether the flaw was exploited between 28 September and 17 November. The saved pull request page also lists a mention on 19 November by a pull request in a public scanner template repository, titled "Add Apache Roller XML-RPC vendor extension detector" and open when read. It is one day before the KEV date (derived). This site did not read that repository and draws no conclusion from it beyond the fact that a public detection request existed by 19 November.
What the project's own pages say, and what they leave out
The security page, saved at about 08:49 UTC on 21 November, lists 18 advisories under 6.1.6 and 15 under 6.1.7. For 6.1.6 it says: "Each affects Apache Roller 6.1.5; users of earlier versions should also upgrade to 6.1.6." That sentence tells earlier users to upgrade. The only saved CVE record that names an earlier release for this flaw came on 17 November. The saved page does not list CVE-2026-129448 at all, four days after that record and a day after the KEV listing. It lists 82384 as "Unauthenticated deserialization in the XML-RPC endpoint", Critical, fixed in 6.1.6.
The page also says: "If you are running an older version, the fix is to upgrade to the current release." The fix for this flaw, as the 129448 record says, is 6.1.6 or later. The current release as the page stood is 6.1.7, which fixes 15 advisories listed as affecting 6.1.6, and "most also affect earlier versions, as each advisory states".
A different deserialisation flaw. One of the 6.1.7 rows is CVE-2026-123374, "Deserialization of untrusted data in weblog update ping responses", rated Important. By its title it is a different flaw in a different component from the XML-RPC one, with its own id. This site saved only the row, not the advisory behind it, so it says no more about that flaw. No saved page says it is exploited, and the KEV entry for 129448 does not name it. It is worth the same upgrade, since it is on the same release line, but it is not what CISA listed.
SAP: a Medium record, 374 days old, that CISA now lists as exploited
The CVE record for CVE-2025-42884 is titled "JNDI Injection vulnerability in SAP NetWeaver Enterprise Portal". SAP published it on 11 November 2025 at 00:14 UTC, a Tuesday, and its own part of the record carries no later update stamp. It says an unauthenticated attacker can inject JNDI environment properties or pass a URL used during JNDI lookup operations, enabling access to an unintended JNDI provider. It continues: "This could further lead to disclosure or modification of information about the server. There is no impact on availability." The affected list holds two entries, "EP-BASIS 7.50" and "EP-RUNTIME 7.50", with no build, support package or upper bound. Its default status is unaffected, so anything else is outside the list.
SAP set the score: CVSS 3.1 base 6.5, Medium: network, low complexity, no privileges, no user interaction, Low confidentiality and Low integrity impact, no availability impact. The vector is in the code block below. This site recomputed the score from the printed vector with the CVSS 3.1 formula and got 6.5. The vector matches Roller's on attack vector, complexity, privileges, user interaction and scope. It differs only in the three impact metrics: Low, Low, None against High, High, High (derived comparison). The record gives no fixed version. Its references are an SAP note (number 3660969, behind an SAP login) and a short link whose text reads sapsecuritypatchday. This site opened neither. The catalogue entry's notes point to SAP's 2025 security notes bulletin page, which this site also did not read. So the saved pages cannot say which SAP patch level closes the flaw.
What CISA says it is. The catalogue entry says SAP NetWeaver Enterprise Portal "contains an improper neutralization of special elements in data query logic vulnerability" that lets an unauthenticated attacker "disclose or modify server information" through injected JNDI properties or a URL used during lookups. CISA-ADP's rating, stamped 20 November, is Exploitation: active, Automatable: yes, Technical Impact: partial. The entry's product field reads "NetWeaver", the record's scope is two Enterprise Portal 7.50 components.
What an attacker gets is not stated. The record says "information about the server" and the entry says "server information". Neither says which information, whether it includes credentials or configuration, or what a portal that holds business data would give up. A Medium score reflects Low confidentiality and Low integrity impact in SAP's rating. CISA's listing says someone has used the flaw. This site cannot reconcile the two and does not guess at the middle.
Labels that do the work of evidence
A label is not a control and not an observation. Six appear in the saved pages, each set against what the pages print.
Labels in the saved Roller, SAP and CISA pages, and what the pages print behind them (read 21 November 2026)
| Label | Where it appears | What the saved pages print |
|---|---|---|
| Medium (6.5) | SAP's CVE record | A score from Low confidentiality and Low integrity impact. Not a statement about exploitation: CISA rates it active |
| Critical (9.8) | Both Roller records | The same score and vector on both ids. It does not say which release each id covers: the two lists differ |
| "a broader range" | CISA's Roller entry | 129448 names more releases than 82384, but not 82384's release, 6.1.5 |
| NetWeaver | CISA's product field for the SAP entry | The description and the record name Enterprise Portal, and the record lists two 7.50 components |
| Data query logic | CISA's vulnerability name for the SAP entry | The record's title says JNDI injection, and the record also prints CWE-943 with the words Improper Neutralization of Special Elements in Data Query Logic |
| Important | Roller 6.1.7 rows on the security page | Apache's own severity scale. The 6.1.7 deserialisation row is Important and the 6.1.6 XML-RPC row is Critical; the page does not show the CVSS behind either |
The Roller id is the sharpest case. An id looks like an identity for a flaw, and here Apache published two for one, with different version lists. An inventory tool, a vulnerability feed and a government catalogue each pick the id they key on. This site found no saved page that links the two ids except the 129448 record and the catalogue's description.
What the catalogue entries set: three days, a directive and a field
Both entries carry the same required action. It begins "Apply mitigations in accordance with vendor instructions", names CISA's directive BOD 26-04 and its "Forensics Triage Requirements", says to follow the directive's guidance for cloud services or discontinue use of the product if mitigations are unavailable, and ends: "Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines." The due date for both is 2026-11-23, 3 days after dateAdded and a Monday; the three days include a weekend (derived). This site did not read the directive or the triage requirements. The entry text does not say whom it binds, so this site reads the date as a deadline for US federal agencies, as it did in its briefing on the 18 November additions, and as a prompt for everyone else.
The catalogue file's count rose from 1,786 in the file that briefing read, released on 18 November at 19:17 UTC, to 1,790 in this one: a net rise of 4 (derived), which matches the four additions of 20 November. Both entries print knownRansomwareCampaignUse as "Unknown", which is not a statement that no ransomware actor uses them.
A field that does not follow the earlier pattern. In the 18 November additions, the three entries with a 3 day due date all printed forensicTriage "Yes" and the one with a 14 day date printed "No". Here the Roller entry prints "Yes" and the SAP entry prints "No", and both are due in 3 days. This site did not read the directive and does not say what the field does. It reports that the SAP entry breaks the pattern those earlier entries showed, and that the pages do not explain why.
The settings and fields the records print
These are the defensive items the saved records print, copied as printed and attributed. The first block is Apache's workaround for people who cannot upgrade at once. It is a setting and a mapping to remove, not a request or an input. The pages print no log lines, hashes, network addresses or other indicators, and this site prints no exploit input, no request and no code from the flawed component.
Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.
The second block lays out, by this site, the version and score fields of the three CVE.org records, one value at a time as printed. Use it to match the three ids against an asset list. The SAP record's affected list has no lower or upper bound inside 7.50.
CVE-2026-82384 assigner apache affected: 6.1.5 fix: Apache Roller 6.1.6 or later
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H baseScore 9.8 CRITICAL
CISA-ADP SSVC 2026-09-28: Exploitation none, Automatable yes, Technical Impact total
CVE-2026-129448 assigner apache affected: 4.0.0 lessThan 6.1.5 fix: Apache Roller 6.1.6 or later
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H baseScore 9.8 CRITICAL
CISA-ADP SSVC 2026-11-18: Exploitation active, Automatable yes, Technical Impact total
CVE-2025-42884 assigner sap affected: EP-BASIS 7.50, EP-RUNTIME 7.50 fix: none listed
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N baseScore 6.5 MEDIUM
CISA-ADP SSVC 2026-11-20: Exploitation active, Automatable yes, Technical Impact partial
The third block is the two catalogue entries' own date and flag fields, from the CISA catalogue file as read on 21 November 2026 (this site laid the values out in lines).
CVE-2026-129448 (vendor Apache, product Roller)
dateAdded: 2026-11-20
dueDate: 2026-11-23
knownRansomwareCampaignUse: Unknown
forensicTriage: Yes
cwes: CWE-502
CVE-2025-42884 (vendor SAP, product NetWeaver)
dateAdded: 2026-11-20
dueDate: 2026-11-23
knownRansomwareCampaignUse: Unknown
forensicTriage: No
cwes: CWE-943
Where the pages differ, with nothing resolved
Seven differences, each as the pages print it.
Differences between the saved Roller, SAP and CISA pages (read 21 November 2026)
| Question | One page says | Another page says |
|---|---|---|
| Which Roller release does the flaw affect? | CVE-2026-82384: Apache Roller 6.1.5 | CVE-2026-129448: 4.0.0 through 6.1.4, and calls it the same vulnerability |
| What did CISA's 'broader range' mean? | CISA's entry: 129448 "applies to a broader range of affected versions" | The 129448 range stops before 6.1.5, the release 82384 names |
| What did the project's page tell earlier users? | 6.1.6 table: "users of earlier versions should also upgrade to 6.1.6" | The only saved CVE record naming an earlier release for the flaw was published on 17 November |
| Is the one flaw exploited? | 82384, CISA-ADP, 28 September: Exploitation none. The record was last updated on 29 September | 129448, CISA-ADP, 18 November: active. The 129448 text says being actively exploited |
| When did the advisory text first exist? | The Roller security page lists 6.1.6 as released 24 September | The 82384 record was published on 28 September. Its CVE Program section lists an oss-security link whose path reads 2026/09/25; this site did not read it |
| How serious is the SAP flaw? | SAP's record: Medium, 6.5 | CISA-ADP: Exploitation active, Automatable yes. CISA lists it |
| What does CISA's forensicTriage field track? | 18 November entries: Yes with 3 days, No with 14 days | 20 November SAP entry: No with 3 days |
What the pages state, and what they do not
Stated and not stated across the saved pages (read 21 November 2026)
| Question | What the saved pages state | What they do not state |
|---|---|---|
| Is Roller exploited? | Apache's 129448 text: being actively exploited. CISA-ADP 18 November: active. KEV entry, 20 November | Who, how many sites, since when, which releases, what the attackers did |
| Is SAP Enterprise Portal exploited? | CISA-ADP 20 November: active. KEV entry, 20 November | The same list. SAP's own record says nothing on exploitation |
| Which Roller releases are affected? | 4.0.0 through 6.1.4 (129448) and 6.1.5 (82384) | Any release before 4.0.0 |
| Is there a Roller fix? | 6.1.6 or later; 6.1.7 the latest on the page | Whether another exploited Roller flaw exists. No page says so |
| Is there a SAP fix? | The record cites an SAP note behind a login. The entry points to SAP's 2025 bulletin page. Neither was read | The fixed version or support package, on any page this site read |
| What does a SAP attacker obtain? | "disclosure or modification of information about the server"; "disclose or modify server information" | Which information, and what it is worth in a real portal |
| How many are exposed? | Nothing counted for either product | Roller sites or Enterprise Portal instances reachable from the internet |
| Why did CISA list them on 20 November? | dateAdded 2026-11-20 on both entries | Any reason or evidence; the entries print none |
| Ransomware use? | knownRansomwareCampaignUse: Unknown on both | Any ransomware group, campaign or victim |
What to do, in order
First what each vendor says, then this site's suggestions, marked as such.
Take this with you
Actions, in the order worth doing
- Roller, Apache's advice: upgrade to Apache Roller 6.1.6 or later. The project's page says older releases are not patched in place and the fix is the current release, which is 6.1.7 as the page stood on 21 November.
- Roller, if you cannot upgrade at once, Apache's workaround: set enabledForExtensions to false in WEB-INF/web.xml, or remove the xmlrpc servlet mapping, and restart. Apache says turning XML-RPC off in the administration UI is not enough.
- This site's suggestion: search inventories and scanners for both Roller ids and by version. The union is 4.0.0 through 6.1.5. A feed keyed on the id CISA lists, 129448, does not name 6.1.5.
- This site's suggestion: treat 6.1.5 hosts with the same urgency as earlier ones. The records call it one flaw (inference), and the exploitation sentence does not say which releases were attacked.
- SAP: apply SAP's note for CVE-2025-42884, which needs an SAP login. The CVE record lists no fixed version, so take the patch level from the note and confirm it on each Enterprise Portal 7.50 system.
- This site's suggestion: find out whether any Enterprise Portal is reachable from outside your network. CISA's required action leaves each asset's internet exposure to the stakeholder.
- This site's suggestion: rank patching by exploitation status, not only by score. A listed flaw rated Medium by its vendor goes ahead of an unlisted flaw rated higher.
- CISA's required action: apply mitigations per the vendor's instructions, in line with BOD 26-04, by 23 November 2026. The entries do not say whom the directive binds and this site did not read it. Check whether it applies to you.
- This site's suggestion: a patch does not answer whether the flaw was used on your systems. The Roller entry prints forensicTriage Yes. If an unpatched Roller or Enterprise Portal faced the internet, plan a review for signs of use as well as the upgrade.
The question the two ids leave open
CISA lists the id that names 4.0.0 through 6.1.4, Apache's first id names 6.1.5, and the fix shipped on 24 September, 57 days before the listing. If your scanner keyed on one of those ids and your catalogue feed keyed on the other, which of your Roller installs would either have told you to act on before 20 November?
Key facts
Sources
- PrimaryCISA KEV catalogue file, catalogVersion 2026.11.20, released 17:48 UTC on 20 November 2026, fetched at about 08:42 UTC on 21 November 2026 and trimmed by this site to the four 20 November entries: required action, due dates, forensicTriage and ransomware fieldsCISA (Known Exploited Vulnerabilities catalogue, JSON)accessed 2026-11-21
- PrimaryApache Roller CVE-2026-129448, published 17 November 2026, updated 21 November 04:55 UTC, read at about 08:48 UTC on 21 November 2026: description, affected range, workaround, CVSS 3.1 9.8, CISA-ADP ratingCVE Program (CVE.org record CVE-2026-129448, assigner Apache)accessed 2026-11-21
- PrimaryApache Roller CVE-2026-82384, published 28 September 2026, updated 29 September, read at about 08:48 UTC on 21 November 2026: description, affected 6.1.5, CVSS 3.1 9.8, CISA-ADP rating noneCVE Program (CVE.org record CVE-2026-82384, assigner Apache)accessed 2026-11-21
- PrimarySAP NetWeaver Enterprise Portal CVE-2025-42884, published 11 November 2025, updated 21 November 2026 04:55 UTC, read at about 08:49 UTC on 21 November 2026: description, affected EP-BASIS and EP-RUNTIME 7.50, CVSS 3.1 6.5, CISA-ADP rating activeCVE Program (CVE.org record CVE-2025-42884, assigner SAP)accessed 2026-11-21
- PrimaryApache Roller security page, a living page, saved at about 08:49 UTC on 21 November 2026: releases 6.1.6 (24 September) and 6.1.7 (11 November 2026), the advisory tables and the supported versions policyApache Roller project (security page)accessed 2026-11-21
- PrimaryPull request 171, saved at about 08:49 UTC on 21 November 2026: opened 29 August 2026, merged 5 September; the change to the XML-RPC endpoint that both CVE records list as the patchApache Roller (GitHub pull request 171)accessed 2026-11-21


