A KEV ticket can close too early when a team equates an installed patch with a corrected attack path. For CVE-2025-42884, closure should show that the affected SAP NetWeaver Enterprise Portal component was identified, the Security Note 3660969 correction was applied at the right support level, and the JNDI provider boundary now behaves as intended.
Vulnerability overview
SAP lists CVE-2025-42884 as a JNDI injection in SAP NetWeaver Enterprise Portal. Security Note 3660969 is the vendor correction. The public bulletin names EP-BASIS 7.50 and EP-RUNTIME 7.50 and assigns CVSS 3.1 6.5. CISA added the issue to KEV on November 20, 2026 with a November 23 due date.
The CVE description says an unauthenticated attacker can inject JNDI environment properties or a URL and cause access to an unintended provider. The scored impact is limited disclosure and modification of server information.
Mechanism and exploitation conditions
The vulnerability requires network reachability and an input path that influences JNDI lookup behavior. Privileges and user interaction are not required by the score. The public record does not disclose the exact request structure or a working exploit.
Before closure, verify those prerequisites against the actual deployment. Document which endpoints accept lookup-related input, which providers are approved, and how the patched system rejects or constrains an unapproved destination. A host-level patch inventory alone does not answer those questions.
Impact
The supported consequences are disclosure or modification of server information. Portal configuration and integration data can affect application behavior, so limited impact is still worth specific containment and validation.
The reviewed sources do not support claims of remote code execution, availability loss, or confirmed credential theft from this CVE. If an incident shows those effects, the evidence should be recorded as a separate finding rather than folded into the vulnerability description.
Affected products and scope
The affected components are EP-BASIS and EP-RUNTIME 7.50. Security Note 3660969 provides the correction, and SAP Support supplies the applicable package details. Teams should attach the component version and note evidence to the ticket.
Custom portal code needs its own closure evidence. Record the JNDI resources it uses, the code path that handles external input, and the result of post-patch testing. Shared platforms may need one inventory entry per portal application because ownership and exposure can differ.
Exposure context
The ZoomEye query app="SAP NetWeaver" produced 71,948 product matches on November 21, 2026, while vul.cve="CVE-2025-42884" produced 0. Exposure is 71,948 under the maximum-count rule. This is a product fingerprint result, not a vulnerable-system result.
The ticket should state that distinction. The external count can help identify hosts for ownership review, but it cannot prove portal version or configuration. Only internal records and validated tests support closure.
Remediation and mitigations
Attach the SAP correction, support-package level, restart evidence, and post-change lookup test to the ticket. Confirm that the portal uses only approved JNDI providers. If restrictions remain, record their owner and removal condition. The public sources do not establish a complete alternate fix.
Add a final exposure check that uses the actual owned hostnames and the corrected state. That evidence is stronger than a general product search and gives the next reviewer a clear basis for accepting the closure.