SAP NetWeaver Portal JNDI injection, exploited

Medium 6.5 Actively exploited Sap Netweaver Enterprise Portal CVE-2025-42884

Actively exploited

Severity 6.5 Reach 10.0 Ease 8.0 Exploitation 10.0 Tooling 0.0

Risk assessment

unauth JNDI injection in SAP NetWeaver Enterprise Portal (CVSS 6.5) is exploited in the wild, exposing or altering server data. Apply SAP's patch now.

By Yazoul AI · automated

What to do

The vendor has published a patch — see the "Vendor Patch" link in the references section. If you cannot patch immediately, review mitigation guidance in this advisory and monitor for exploitation attempts.

Actively exploited in the wild - CVE-2025-42884 is a medium-severity JNDI injection flaw in SAP NetWeaver Enterprise Portal that lets an unauthenticated remote attacker redirect JNDI lookups to an unintended provider, exposing or altering server information. SAP has released a patch; apply it now given confirmed exploitation.

Overview

SAP NetWeaver Enterprise Portal is the front door to many enterprise landscapes: it hosts role-based workspaces, federated identity, and connections to backend systems. CVE-2025-42884 lets an attacker who can reach the portal over the network send requests that inject JNDI environment properties or supply a URL used during a JNDI lookup. The portal then resolves that lookup through an unintended JNDI provider chosen by the attacker.

JNDI (Java Naming and Directory Interface) is the Java mechanism applications use to look up objects such as data sources and directory entries by name. When an application lets user-supplied input influence that lookup, the attacker controls where the resolution goes and, depending on the provider, can reach services the portal should never talk to.

Impact

  • Confidentiality: an attacker can cause the portal to disclose information about the server or the systems it connects to.
  • Integrity: injected properties or a redirected lookup can modify information the portal returns or stores.
  • Availability: SAP states there is no availability impact.

The CVSS score is 6.5 (network vector, low complexity, no privileges, no user interaction), so any internet- or intranet-reachable portal is a candidate target. The CISA KEV listing confirms real-world exploitation, even though the community EPSS estimate for near-term exploitation is only about 0.3%. Treat KEV as the stronger signal: someone is already using this.

Remediation and Mitigation

  1. Patch. Apply the SAP Security Note for CVE-2025-42884 to every NetWeaver Enterprise Portal instance. This is the only complete fix.
  2. Reduce exposure. Do not expose the portal directly to the internet. Put it behind a reverse proxy or VPN, and restrict access to known user networks.
  3. Monitor. Review portal and application server logs for unusual JNDI lookup errors, unexpected outbound connections to LDAP, RMI, or directory services, and requests containing JNDI-style parameters.
  4. Segment. Ensure the portal host cannot reach untrusted naming or directory services on the network, so a redirected lookup has nowhere useful to go.
  5. Inventory. Older portal deployments are often forgotten. Check for instances outside your standard patch cycle.

Security Insight

This bug sits where two long-running problems meet: JNDI injection, still appearing decades after log4shell made it famous, and SAP’s sprawling NetWeaver estate, where old portal instances linger unpatched. The KEV listing shows attackers still scan for Java naming-layer weaknesses on enterprise middleware. It also follows SAP’s recent supply-chain trouble in its npm ecosystem, reinforcing that defenders should watch every SAP component - not just the ERP core - as an active attack surface.

Related: SAP npm packages compromised in credential-stealing attack and SAP ransomware claim by thegentlemen (Oct 2026).

Further Reading

Share

Get a Telegram alert when the next one lands: SAP advisories

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.