Research

CISA Lists a Year-Old SAP Enterprise Portal Flaw as Exploited: CVE-2025-42884, Fixed by Note 3660969 on November 11, 2025. The Federal Deadline Is Monday.

CISA Lists a Year-Old SAP Enterprise Portal Flaw as Exploited: CVE-2025-42884, Fixed by Note 3660969 on November 11, 2025. The Federal Deadline Is Monday.

If you run SAP NetWeaver Enterprise Portal 7.50, confirm today that SAP Security Note 3660969 is applied, starting with any portal that strangers can reach. CISA added CVE-2025-42884 to its Known Exploited Vulnerabilities catalog on Friday, November 20, 2026, and gave federal agencies until Monday, November 23 to fix it. That is a three-day deadline. The fix itself is not new: SAP shipped it on its November 2025 Patch Day, Tuesday, November 11, 2025, which makes it 374 days old on the day CISA listed it.

That is the pattern we measured this week in Misplaced Trust: of 187 vulnerabilities with first exploitation evidence dated November 13 through 20, the median had been public for 640 days, and more than half were over a year old. This one is a year old. The fix has been waiting for a year.

What CISA says

The catalog entry (catalog version 2026.11.20, released November 20 at 17:48 UTC) names it "SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability", filed under CWE-943. CISA's description: SAP NetWeaver Enterprise Portal "allows an unauthenticated attacker to disclose or modify server information via injected JNDI environment properties or a URL used during JNDI lookup operations." Known ransomware use is marked unknown. The required action is to apply the vendor's fix under BOD 26-04, CISA's directive for federal civilian agencies, which CISA also recommends to everyone else.

It was listed alongside three others the same day, all with the same Monday deadline: Cisco Expressway Series CVE-2026-76466 (hard-coded credentials), VMware vCenter CVE-2026-123890 (authentication bypass in the directory service) and Apache Roller CVE-2026-129448 (deserialization in the XML-RPC endpoint). One small difference in the catalog: the other three carry CISA's "forensics triage" flag; the SAP entry does not.

CISA's alert says the four were added "based on evidence of active exploitation". It does not say who saw the exploitation, against whom, or how. Neither did any source we could read. We are not going to guess.

What the flaw is

SAP's own description, from the NVD record it supplied: the Enterprise Portal "allows an unauthenticated attacker to inject JNDI environment properties or pass a URL used during JNDI lookup operations, enabling access to an unintended JNDI provider. This could further lead to disclosure or modification of information about the server. There is no impact on availability."

In plain terms: JNDI is the Java lookup service an application server uses to find resources by name. If a stranger can choose where that lookup goes, the server can be made to talk to a directory the attacker controls. That is the family Log4Shell belonged to. SAP scores this one much lower than that: CVSS 3.1 of 6.5, Medium, vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. Network reachable, no login, no user click, limited confidentiality and integrity impact. CISA's coordinator scoring on the NVD record adds "exploitation: active" and "automatable: yes".

A Medium score is exactly the kind of fix that sits in the queue for a year. CISA listing it is the signal that someone is using it anyway.

Who is exposed

  • Product and releases. SAP NetWeaver Enterprise Portal, software components EP-BASIS 7.50 and EP-RUNTIME 7.50, per SAP's November 2025 Patch Day table and the NVD record. The portal runs on the AS Java stack. Onapsis lists the SAP support component as EP-PIN-APF-CAT.
  • Reachability. No login is needed, so anyone who can reach the portal's HTTP or HTTPS port can try. Enterprise Portal is often the employee or partner front door and is frequently published to the internet, usually under paths beginning with /irj/. Internet-facing portals are first in line; internal-only portals are next, because anyone already inside your network can reach them.
  • Not affected by this CVE. ABAP-only systems with no Enterprise Portal, and SAP products other than the portal. That does not make them safe from the other SAP flaws in the news.

We did not count exposed portals on the internet, so we are giving no number.

The fix

Apply SAP Security Note 3660969, released November 11, 2025 (SAP's Patch Day table lists it as Medium, CVSS 6.5, alongside 17 other new notes that day). Onapsis Research Labs found and reported the flaw, per its own Patch Day write-up.

What we could not read: the note itself sits behind SAP's support login, so we have not seen its exact fixed support package and patch levels, or whether it offers a workaround. Onapsis's public write-up does not mention a workaround. SecurityBridge's November 2025 write-up returned HTTP 403 to us. If you have an S-user, the note's support package table is the authority on which patch level you need.

Am I affected?

  1. Find every Enterprise Portal you run. Include production, QA, sandbox and any partner or supplier portal. A forgotten test portal on the internet counts.
  2. Read the deployed component versions. On AS Java, open SAP NetWeaver Administrator (the /nwa path on the portal host), go to Troubleshooting, then Java, then System Information, and look up the software components EP-BASIS and EP-RUNTIME. Note the release (7.50), the support package and the patch level. Compare them to the table in Note 3660969.
  3. About SNOTE. Transaction SNOTE is the Note Assistant for ABAP systems. Enterprise Portal is Java, so a Java fix like this one usually arrives as patched software component archives deployed with SAP's Software Update Manager, not as an SNOTE correction. If SNOTE on an ABAP system shows the note as "cannot be implemented", that does not tell you the portal is fixed. Check the Java components as in step 2.
  4. Use Solution Manager if you have it. System Recommendations in SAP Solution Manager checks connected Java systems against security notes and should list Note 3660969 as relevant for any unpatched portal.
  5. Look for signs it was used. This part is our reasoning from the description, not published guidance, because no exploit details have been published. In the portal's HTTP access logs, look for unauthenticated requests carrying JNDI-style strings such as ldap://, rmi:// or java.naming. In firewall or proxy logs, look for the portal host making outbound connections to unfamiliar addresses on directory or RMI ports (389, 636, 1389, 1099). A portal server has little reason to start LDAP or RMI sessions to the internet.
  6. If you cannot patch by Monday, take the portal off the internet or put it behind a VPN or authenticating proxy until you can. That is general hygiene, not an SAP workaround.

Indicators

None were published in the sources we read, so we added nothing to the feed. The CVE syncs into our KEV index on its own and we do not hand-ingest CVEs.

What our edge saw

Nothing we can attribute to this CVE, and we want to be exact about why. Our harvester holds no public proof-of-concept for CVE-2025-42884, so there is no exploit path to match against. As a broader look, we scanned every request our edge recorded from October 21 to November 20 for paths beginning with /irj/ (the usual portal prefix): 0 of 631,218 edge blocks, 0 of 103,551 edge canary hits, 0 of 693 requests that reached our origin. We run no SAP, so nobody has much reason to aim SAP traffic at us, and we have no SAP decoy. A zero here means we were not probed on that path, not that nobody is scanning for portals.

Is this in our November 10 SAP post?

No. Our November 10 SAP Patch Day post covered the November 2026 notes, a different set of bugs. It does not mention CVE-2025-42884. We have no earlier post on this CVE.

How we know

  • CISA KEV JSON, catalog 2026.11.20, read November 20, 2026: dateAdded 2026-11-20 (Friday), dueDate 2026-11-23 (Monday), for all four entries.
  • CISA alert of November 20, 2026, "CISA Adds Four Known Exploited Vulnerabilities to Catalog".
  • NVD record for CVE-2025-42884: published November 11, 2025, CNA SAP, CVSS 3.1 6.5, references Note 3660969.
  • SAP's 2025 Security Notes bulletin (support.sap.com), November 2025 section: Note 3660969, JNDI Injection vulnerability in SAP NetWeaver Enterprise Portal, EP-BASIS 7.50 and EP-RUNTIME 7.50, Medium, 6.5.
  • Onapsis, SAP Security Patch Day November 2025 (published November 11, 2025): credits Onapsis Research Labs with the find.
  • Not read: SAP Note 3660969 itself (login required) and SecurityBridge's write-up (HTTP 403).

Our numbers cover only what is named above. Something in here is probably wrong; if you can read the note and it says otherwise, follow the note, and tell us.

Read next: Misplaced Trust: this week's exploited bugs were a median 640 days old.


Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.

Get your free key → analytics.dugganusa.com/stix/register