SAP NetWeaver Portal's JNDI Injection Is a Trust-Boundary Problem
CVE-2025-42884 is a medium-scored SAP NetWeaver Enterprise Portal vulnerability that became urgent in November 2026 when CISA added it to the Known Exploited Vulnerabilities catalog. The flaw affects EP-BASIS and EP-RUNTIME 7.50 and allows an unauthenticated attacker to inject JNDI environment properties or a URL used during JNDI lookup.
The immediate consequence is disclosure or modification of server information. The more important consequence is trust movement. A Java application that resolves names through JNDI may consult directory services, remote naming providers, or environment-supplied configuration. If an attacker can influence the lookup target, the application may connect to an unintended provider or expose data that was meant to stay inside the server's identity and configuration boundary.
SAP's security note 3660969 covers the defect. The SAP bulletin assigns CVSS 3.1 a score of 6.5 and classifies the issue as a JNDI injection in SAP NetWeaver Enterprise Portal. The lower score does not make a known-exploited portal safe, particularly when the service is reachable from a broad network or is used as an administrative entry point.
Why score and priority diverge
CVSS describes technical impact and exploit prerequisites. An exploited-vulnerability listing describes what defenders now know is happening. Those signals answer different questions. A medium-severity flaw on a portal that exposes directory metadata, application links, and server identifiers can provide reconnaissance or a configuration foothold that helps a later attack.
The prerequisite is named and concrete: the attacker must reach the vulnerable portal path and control input that reaches JNDI resolution. The advisory does not establish that every EP-RUNTIME or EP-BASIS installation is internet-facing, and it does not prove that an observed exposure has been exploited.
Review the deployment as a whole
Inventory every NetWeaver Enterprise Portal 7.50 system, including test systems that share production directory data, reverse-proxy paths, or administrator accounts. Confirm that security note 3660969 is implemented in the running software, not only in a change ticket.
Check the external and internal network paths to the portal. A reverse proxy that exposes only a login page does not necessarily protect every application route. Review JNDI providers, Java system properties, and environment values for unintended remote endpoints. Restrict outbound traffic from the application server to approved naming and directory services.
For investigation, collect portal access logs, Java process arguments, JNDI and LDAP client activity, outbound connections, and changes to application configuration. Review unfamiliar account or directory lookups around the first suspicious request. If the portal is confirmed compromised, rotate credentials and trust material available to the application, then rebuild from a known-good image where necessary.
The durable fix is patch management plus a narrower naming-provider policy. JNDI must resolve names the application expects, through services the operator controls, with no path for request data to select an arbitrary provider.

