Actively exploited CVSS 6.5 Security news
SAP NetWeaver Enterprise Portal: year-old flaw CVE-2025-42884 is being exploited, CISA says
On 20 November 2026 the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-42884, a flaw in SAP NetWeaver Enterprise Portal, to its catalog of actively exploited vulnerabilities. The bug is not new: SAP fixed it on 11 November 2025 in security note 3660969 and rates it medium (CVSS 6.5). An unauthenticated attacker can feed the portal their own JNDI lookup settings and read or modify information about the server. If you never got round to that note, now is the time.
Key points
- Affected: SAP NetWeaver Enterprise Portal 7.50 (EP-BASIS, EP-RUNTIME) – corporate portals on SAP NetWeaver AS Java that lack note 3660969.
- The bug: an unauthenticated attacker can inject JNDI environment properties, or a URL the portal uses for a JNDI lookup (CWE-943). Impact per SAP: disclosure and modification of server information, no availability impact.
- Exploited: yes, according to CISA – in the KEV catalog since 20 Nov 2026 with a 23 Nov deadline for US federal agencies. Neither CISA nor SAP says who is attacking or how.
- A fix has existed since 11 Nov 2025 (SAP Security Patch Day). The flaw was found by Onapsis Research Labs.
Vulnerabilities: CVE-2025-42884
What happened
On Friday 20 November 2026 the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-42884 in SAP NetWeaver Enterprise Portal to its Known Exploited Vulnerabilities catalog (KEV, version 2026.11.20). A KEV listing means CISA has evidence of attacks in the wild. US federal agencies have until 23 November 2026 – three days – to deal with it. CISA lists ransomware use as "unknown" and has published no details about the attacks themselves.
The flaw itself is not new. SAP fixed it on 11 November 2025 as part of its November 2025 Security Patch Day, in security note 3660969. It was discovered by Onapsis Research Labs. SAP and NVD rate it medium: CVSS 3.1 6.5. That is exactly the kind of score that pushes a patch down the queue – and we now know attackers are interested in it.
Technical details
This is based on the NVD entry, the CISA catalog and the Onapsis write-up. We do not publish exploitation instructions.
- Component: SAP NetWeaver Enterprise Portal 7.50 – the corporate portal running on the SAP NetWeaver AS Java application server.
- Type of flaw: improper neutralisation of special elements in data query logic (CWE-943), specifically JNDI injection. JNDI is the Java interface applications use to look up resources such as database connections, directory services and objects.
- Conditions: the attacker does not need to be logged in and no user interaction is required; network access to the portal is enough (vector
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). - How an attack works: the attacker supplies their own JNDI environment properties, or a URL the portal then uses for a lookup. The portal can end up talking to a different JNDI provider from the one its developers intended.
- Impact per SAP: disclosure or modification of information about the server; availability is not affected. Neither SAP nor CISA describes this as code execution.
Who is affected
columns: Product | Version | Status
row: SAP NetWeaver Enterprise Portal (EP-BASIS, EP-RUNTIME) | 7.50 without note 3660969 | vulnerable
row: SAP NetWeaver Enterprise Portal (EP-BASIS, EP-RUNTIME) | 7.50 with note 3660969 | fixed
- Organisations running Enterprise Portal on SAP NetWeaver AS Java – typically the front door for staff and partners into SAP systems, and often reachable from the internet.
- ABAP and S/4HANA systems without the portal are not listed as affected in the NVD entry.
- According to Onapsis, the fix belongs to component EP-PIN-APF-CAT.
How to tell if you were compromised
Neither CISA nor SAP has published indicators of compromise. What we suggest checking (our own advice):
- Patch status: use SAP Note Assistant or your list of implemented notes to confirm that note 3660969 is in place on every portal instance.
- Access logs of the portal and any reverse proxy: unusual unauthenticated requests containing URLs with
ldap://,rmi://,iiop://ordns://schemes, or JNDI property names such asjava.naming.provider.url. - Outbound connections from the AS Java server to unknown addresses, especially to LDAP (389, 636) and RMI (1099) ports on the internet – a portal normally has no need for them.
- Configuration changes to the portal and server that your administrators did not make.
Pull suspicious addresses and domains out of your logs with our IOC extractor, and break down the vector in our CVSS calculator.
What to do
- Apply SAP security note 3660969 on every Enterprise Portal 7.50 instance. The fix has been available since November 2025.
- Restrict access to the portal. If it does not need to be on the internet, put it behind a VPN or limit it to the corporate network.
- Block outbound connections from the AS Java server that it does not need – this limits abuse via a rogue JNDI provider.
- Review logs after patching as described above. Attacks may have happened before the note was applied.
- Check your other SAP patches too – especially the November 2026 Patch Day with four CVSS 10 flaws.
Timeline
Update
- 20 Nov 2026 – first version of this article.
FAQ
Why is a medium-severity CVSS 6.5 bug in the exploited catalog?
CISA's KEV catalog is not ranked by score; a flaw goes in when CISA has reliable evidence of exploitation. CVSS only describes the technical properties of a bug. An unauthenticated flaw on an internet-facing portal is useful to attackers even with a medium score – for example as a first step in reconnaissance.
I run SAP S/4HANA. Does this affect me?
Only if you also run SAP NetWeaver Enterprise Portal 7.50 on the AS Java stack. Both the NVD entry and SAP's rating list EP-BASIS 7.50 and EP-RUNTIME 7.50 as the affected components. ABAP systems without the portal are not listed.
Have CISA or SAP published indicators of compromise?
No. The catalog only gives a description, a deadline and an instruction to apply the vendor's fix. What to look for in logs and network traffic is covered under How to tell if you were compromised – that is our advice, not guidance from SAP or CISA.
Sources
Spotted a mistake? Let us know and we will correct it openly.