SAP NetWeaver Enterprise Portal: JNDI flaw exploited (CISA KEV)
CISA confirms exploitation of CVE-2025-42884 in SAP NetWeaver Enterprise Portal 7.50: unauthenticated JNDI injection. US federal deadline is 23 November.

On 20 November 2026 the US CISA added CVE-2025-42884, a vulnerability in SAP NetWeaver Enterprise Portal, to its Known Exploited Vulnerabilities (KEV) catalog. According to the National Vulnerability Database (NVD) description, an unauthenticated attacker can inject JNDI environment properties or pass a URL used during JNDI lookup operations, making the server access an unintended JNDI provider. Inclusion in the catalog means CISA has evidence of real-world exploitation.
This article is based on a single source: the CISA entry in the KEV catalog, with NVD data. The entry does not say who is exploiting the flaw, against which organisations, since when or with which tools.
What the KEV entry says
- Name: SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability.
- Added to the catalog: 20 November 2026.
- Deadline for US federal agencies: 23 November 2026, three days after inclusion.
- Use in ransomware campaigns: unknown («Unknown»).
- Required action: apply mitigations according to vendor instructions, in line with CISA’s BOD 26-04 directive on prioritising security updates based on risk and its «Forensics Triage Requirements»; for cloud services, follow the same directive, or discontinue use of the product if mitigations are unavailable. CISA also asks organisations to assess the internet exposure of each asset.
The reference to forensic triage requirements means that updating is not enough: you also need to check whether the system has already been compromised.
Technical details
JNDI (Java Naming and Directory Interface) is the interface Java applications use to look up objects and resources in naming and directory services. In the case of CVE-2025-42884, according to the NVD, the attacker can influence these lookups in two ways: by injecting JNDI environment properties or by supplying the URL used in the lookup. The result is access to a JNDI provider other than the intended one.
The entry lists the possible consequences as disclosure or modification of information about the server, with no impact on availability.
- Weakness: CWE-943, improper neutralization of special elements in data query logic.
- CVSS 3.1: 6.5 (medium), assigned by SAP, vector
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N: network attack, low complexity, no privileges required, no user interaction, low impact on confidentiality and integrity, none on availability. - NVD entry status: published on 11 November 2025, last modified on 20 November 2026, analysis completed («Analyzed»).
The score is medium, but inclusion in the KEV catalog confirms exploitation: when setting priorities, this matters more than the CVSS score alone. The entry does not say whether the flaw was used on its own or together with others. In MITRE ATT&CK terms, exploiting a network-reachable service without authentication corresponds to T1190 (Exploit Public-Facing Application). The entry does not include public indicators of compromise.
Affected versions and fix
According to the NVD, SAP NetWeaver Enterprise Portal 7.50 is affected. The entry’s references include SAP Note 3660969, available only with access to the SAP support portal, and SAP’s Security Patch Day page.
The NVD entry has existed since 11 November 2025: confirmed exploitation therefore comes about a year after publication. If you already applied the SAP note during that period, you should still check that you were not hit before the update.
What it means for European companies
SAP NetWeaver is the technology platform for many SAP applications, which are widespread among European and Italian companies too; the Enterprise Portal gives users a web access point to those applications. The NVD rates the impact on confidentiality and integrity as low, but the attacker needs no credentials and the affected server is part of the company’s SAP environment.
The KEV catalog is binding only for US federal agencies, but it is a widely used reference for prioritising updates. For organisations subject to NIS2 (in Italy, Legislative Decree 138/2024), a flaw with confirmed exploitation in a business management system should be treated as a high priority, regardless of its medium score.
What to do now
- Inventory: check whether you run SAP NetWeaver Enterprise Portal 7.50 in your environments, including those managed by partners or suppliers.
- Fix: apply the correction indicated by SAP in Note 3660969, following the vendor’s instructions. If you work with an SAP partner, ask them to confirm that the note is installed on all systems.
- Exposure: assess whether the portal is reachable from the internet or from untrusted networks and, until the fix is applied, consider restricting access to the networks that actually need it.
- Look for compromise, as CISA requires with forensic triage: if you log requests to the portal, look for unauthenticated requests containing JNDI URLs or properties in their parameters; also check for unusual outbound connections from the portal server and unexpected changes to its configuration.
- If you find suspicious signs, treat the event as an incident: the fix does not remove access that has already been obtained. Assess your notification obligations.
How ARXDOME helps
ARX Expose shows what can be seen of your company from outside, with open ports, recognised products and known vulnerabilities on public services: it is the starting point to understand whether the portal is reachable from the internet. ARX Shield reports open vulnerabilities per machine and per package, with those already exploited highlighted. On monitored servers, ARX Sentry checks file integrity in the chosen folders and ARX Trace enables collection and searches across multiple machines to verify whether compromises have occurred.
Last updated:


