On this page (7 sections)
CISA has added CVE-2025-42884, a flaw in SAP NetWeaver Enterprise Portal, to its Known Exploited Vulnerabilities (KEV) catalog, with a date added of 2026-11-20. The weakness lets an unauthenticated attacker inject JNDI environment properties or a URL used during JNDI lookups, which can lead to disclosure or modification of information about the server. The CVE was published on 2025-11-11, and its references point to SAP Note 3660969 and SAP's security patch day page.
If your organization runs SAP NetWeaver with the Enterprise Portal component, especially where it is reachable from the internet, this belongs near the top of your patching queue. The public sources we reviewed are thin on technical detail, so this article separates what is confirmed from what is not.
What happened
According to the NVD entry, SAP NetWeaver Enterprise Portal contains an improper neutralization of special elements in data query logic vulnerability. An unauthenticated attacker can disclose or modify server information through injected JNDI environment properties or a URL used during JNDI lookup operations.
The GitHub advisory was published on 2025-11-11 and lists SAP Note 3660969 and SAP's security patch day page as references. We could not review the content of that note, so we cannot say what corrections, workarounds or version details it contains. The CISA KEV entry lists a due date of 2026-11-23 and shows known ransomware campaign use as Unknown.
Technical details in plain terms
JNDI (Java Naming and Directory Interface) is a Java API that applications use to look up resources such as databases, directories or other services by name. A lookup is meant to resolve only to providers the application intends to use.
Per the advisory text, this flaw lets an attacker supply JNDI environment properties or a URL that is used during a lookup, enabling access to an unintended JNDI provider. The weakness is classed as CWE-943: special elements in input are not neutralized, so they can change the logic of a query the application builds.
The CVSS v3.1 metrics in the GitHub advisory describe a network-reachable attack with low complexity, no privileges required and no user interaction. Impact is rated low for confidentiality and low for integrity, with none for availability, which is why the score is 6.5 rather than critical. A medium score should not lull you into waiting: CVSS measures technical severity, not whether attackers are using the bug, and the KEV listing means CISA has it in its exploited catalog.
The GitHub advisory also shows an EPSS score of 0.276% (20th percentile) as of its last update in November 2025. That predates the KEV listing and should not be used to judge urgency today.
Who is affected
The affected component is SAP NetWeaver Enterprise Portal. The sources reviewed do not list affected release numbers or patch levels, and the GitHub advisory shows affected and patched versions as unknown. You cannot rule yourself in or out by version from this article alone, so confirm against SAP's own guidance, starting with the referenced SAP Note 3660969 and SAP's security patch day page.
Realistic exposure is highest for:
- Portals published to the internet or to partners without a reverse proxy or filtering layer in front
- Organizations that have not yet reviewed SAP's guidance for this CVE
- Environments where the portal is poorly inventoried, such as older landscapes run by another team or a hosting provider
How to check your exposure
Start with inventory, then compare against SAP's guidance. None of these steps require changing the portal.
- Identify every SAP NetWeaver system in your landscape and note whether the Enterprise Portal component is installed and which URLs are reachable from outside your network.
- Look up SAP Note 3660969 through your SAP support channel and compare it with the software component versions and support package levels you run. We could not verify what the note contains.
- Check your change records for any SAP correction applied for CVE-2025-42884. If you cannot confirm one, assume the system is not yet addressed.
- Review web server, reverse proxy and portal logs since the CVE was published on 2025-11-11 for anything unusual on portal endpoints. Because no indicators of compromise are published, look for activity you cannot explain rather than for a specific pattern.
What to do now
CISA's KEV entry calls for applying mitigations in accordance with vendor instructions and sets a due date of 2026-11-23. Even if you are not bound by that directive, the same urgency makes sense for internet-facing portals.
- Review SAP Note 3660969 and SAP's security patch day page, and apply the vendor's mitigation or correction to every affected NetWeaver Enterprise Portal system, starting with internet-facing ones.
- If you cannot apply it immediately, limit who can reach the portal (trusted networks or VPN) and put a filtering layer in front of it, as a stopgap and not a replacement for SAP's fix.
- Review portal and proxy logs back to 2025-11-11 for activity you cannot explain, and preserve them before rotating or archiving.
- If you find signs of compromise, treat the host as compromised: isolate it, rotate credentials and secrets the portal could read, and follow your incident response plan.
- Track SAP's security patch day notices so future corrections are applied on a schedule.
- Record the patch level and date for each system so you can show it was addressed.
Detection and monitoring afterwards
Applying SAP's fix addresses the vulnerability going forward but does not tell you whether someone used it earlier. The CVE has been public since November 2025 and appears in CISA's exploited catalog from 2026-11-20, so look backward as well as forward.
- Keep portal and proxy logs long enough to cover at least the period since 2025-11-11.
- As general hardening, not a known indicator for this CVE, alert on new outbound destinations from SAP servers.
- Watch for unexpected changes to portal configuration or server information that no one on your team made.
- Monitor certificates, DNS records and response headers on your public portal hostnames so unplanned changes are noticed quickly. Webforta Monitor covers certificate, DNS and header-change monitoring for sites you run, and the free SSL checker gives a quick look at a hostname's certificate.
A web application firewall can add a filtering layer in front of web-facing applications, as explained in what is a WAF, but it is not a substitute for applying SAP's fix.
What we do not know yet
- Which exact NetWeaver Enterprise Portal versions are affected and which are fixed; the public records we reviewed do not say.
- What SAP Note 3660969 contains, since we could not review it.
- Who is exploiting the flaw, how widely, and to what end.
- Whether exploitation is chained with other bugs. The sources do not say.
- Whether ransomware groups use it. CISA lists this as Unknown.
We will not guess at these. Check SAP's note and CISA's catalog entry for updates.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
