JNDI lookup control after the SAP NetWeaver KEV listing

The CISA KEV addition for CVE-2025-42884 puts a public deadline on a configuration problem that SAP teams may have treated as a routine patch. The issue concerns JNDI lookup control in SAP NetWeaver Enterprise Portal. The technical response should restore the expected provider boundary and prove that an untrusted value can no longer redirect the lookup.

Vulnerability overview

SAP's March 2025 patch-day bulletin lists Security Note 3660969 for a JNDI injection in SAP NetWeaver Enterprise Portal. EP-BASIS 7.50 and EP-RUNTIME 7.50 are named. The CVSS 3.1 score is 6.5 with network access, no privileges, and no user interaction.

CISA added CVE-2025-42884 to KEV on November 20, 2026 and set November 23 as the federal remediation due date. The catalog describes disclosure or modification of server information through injected JNDI properties or a lookup URL.

Mechanism and exploitation conditions

The public CVE text says an attacker can inject JNDI environment properties or pass a URL used in a lookup, enabling access to an unintended provider. That means the flaw is about where a lookup goes and which inputs influence that destination. It does not provide a request-level exploit recipe.

Teams should identify lookup paths that accept external input, then review the provider configuration around them. A path that cannot reach attacker-controlled data may still be relevant to defense in depth, but it should not be described as confirmed exploitable without evidence.

Impact

The scored impact is limited disclosure and modification. In a portal, that can affect the integrity of returned configuration and the confidentiality of server-side data. The impact can grow if the unintended provider is outside the enterprise trust boundary.

The reviewed sources do not show availability impact, remote code execution, or credential theft. Those outcomes may be investigated in a real incident, but they should not be attributed to this CVE based on the current record.

Affected products and scope

The affected components are EP-BASIS and EP-RUNTIME 7.50. Security Note 3660969 controls the support-package correction. The public bulletin does not supply a complete matrix, so asset owners should use the note and SAP support records rather than guessing from a base release.

Scope should include standard portal code and custom integrations. A JNDI provider can be defined in application configuration, environment settings, or code. Each path needs an owner and a validation method because the platform patch may not cover every locally built lookup path.

Exposure context

The ZoomEye Search app="SAP NetWeaver" returned 71,948 product fingerprint matches on November 21, 2026. The filter vul.cve="CVE-2025-42884" returned 0. Exposure is 71,948, using the maximum selected query. This is not a confirmed vulnerable count.

The number helps an organization ask whether its external SAP footprint is understood. It does not show whether a host runs Enterprise Portal, whether the affected components are installed, or whether a lookup path is reachable. Those facts come from owned systems and vendor records.

Remediation and mitigations

Apply the SAP correction and verify the actual support package. Restrict JNDI providers to an approved list and block outbound lookup destinations that are not required. Review logs for unexpected provider access during the period when the system was exposed.

After the fix, repeat a controlled lookup test with the production configuration. Preserve the test evidence and the note version used. The reviewed sources do not validate a non-vendor substitute, so any network restriction should be labeled as an interim control until the correction is complete.

References