What happened
CVE-2025-42884 affects the Enterprise Portal component of the SAP NetWeaver platform. Enterprise Portal is a web portal companies use to give employees, partners or customers access to applications and data from their SAP systems. The flaw appeared in the US National Vulnerability Database (NVD) on November 11, 2025, and points to SAP Security Note 3660969.
According to SAP’s description, an attacker without any login can feed the portal their own settings or an address used for so-called JNDI lookups. The portal may then reach out to a source it was never meant to talk to. This can lead to disclosure or modification of information about the server. SAP states there is no impact on availability.
The flaw has been public for more than a year, but the US agency CISA only added it to its catalog of actively exploited vulnerabilities on November 20, 2026. ENISA’s European vulnerability database EUVD has also listed it as exploited since the same day, under EUVD-2025-60994. Neither CISA nor ENISA has published details about the attacks or who is behind them.
Why it is dangerous
The flaw is classified as CWE-943, improper neutralization of special elements in data query logic. Put simply, the application takes input from outside and uses it in a lookup without checking it properly.
JNDI (Java Naming and Directory Interface) is the mechanism Java applications use to find resources such as database connections or configuration. Think of it as a phone book. With this flaw, an attacker can hand the portal their own phone book or tell it which phone book to look in. The portal may then get answers from someone it should never trust.
Key conditions based on SAP’s assessment:
- The attack works over the network, including the internet if the portal is publicly reachable.
- The attacker needs no login and no action from any user.
- They can read or change some information about the server. SAP rates the impact on confidentiality and integrity as low.
- The flaw does not cause an outage.
- SAP’s description does not mention code execution or full server takeover.
The CVSS score rates severity on a scale from 0 to 10. For this flaw it is 6.5, medium severity under CVSS 3.1, and it was assigned by SAP itself. The number alone does not tell the whole story, since information about a server can give an attacker a foothold for further steps.
The CISA KEV catalog (Known Exploited Vulnerabilities) only lists flaws that CISA knows are being exploited in real attacks. Whether this one is used in ransomware campaigns is currently unknown to CISA. EPSS is a statistical estimate of the likelihood of exploitation in the next 30 days. As of November 20, 2026, it stands at 0.28%, higher than about 20% of scored vulnerabilities. Confirmed exploitation in KEV outweighs this estimate.
Who is affected
This affects organizations running SAP NetWeaver Enterprise Portal, often simply called “SAP Portal”. These are mostly mid-sized and larger companies, manufacturers, distributors and public sector bodies that use SAP and give employees and partners access to applications through the portal.
Portals reachable from the internet, for example for suppliers, customers or remote staff, are at the highest risk. A portal available only on the internal network is less exposed, but an attacker who gets into the network another way can still target it.
SAP lists the exact affected versions in Note 3660969, available after logging in to SAP for Me. According to SAP’s description, the flaw is in the Enterprise Portal component. If your organization does not use SAP at all, this flaw does not affect you. If an external partner manages your SAP system, ask them directly.
How to check if you are affected
First, find out whether Enterprise Portal runs in your environment. It is usually reachable at an address ending in /irj/portal. From a computer outside your company network, you can check whether the portal answers from the internet. The command only fetches response headers and changes nothing:
curl -sI https://portal.yourcompany.com/irj/portal
You can find the version and Support Package level by logging in as an administrator in a browser and opening the system information page. The page only displays data:
https://<server>:<port>/monitoring/SystemInfo
The same details are available in SAP NetWeaver Administrator under system information. If you use SAP Solution Manager or SAP Focused Run, the System Recommendations tool shows whether Note 3660969 is missing. Compare your version with the list in the note.
How to fix it
SAP released the fix in Security Note 3660969. CISA requires applying mitigations according to vendor instructions, or discontinuing use of the product if mitigations are unavailable. US federal agencies have a deadline of November 23, 2026. That is a useful benchmark for how quickly you should act.
Work in this order:
- Find out whether you run Enterprise Portal and whether it is reachable from the internet. Deal with publicly reachable systems first.
- Log in to SAP for Me, open Note 3660969 and check which versions are affected, which package fixes the flaw and whether SAP lists a workaround.
- Deploy the fix through your standard process, ideally on a test system first and on production right after.
- If you cannot patch right away, restrict internet access to the portal (VPN, firewall, IP allowlists) and allow outbound connections from the server only where truly needed. These are general measures, not SAP guidance.
- After patching, look for signs of compromise as described in the next section.
SAP states that low and medium priority notes contain the fix in at least the newest support package of all releases in mainstream or extended maintenance. If you run an old, unsupported version, a fix may not exist for it and you should plan an upgrade.
What if you may already be compromised
Neither SAP nor CISA has published specific indicators of compromise such as IP addresses or files. The flaw has been known since November 2025 and is now confirmed as exploited, so it is worth reviewing the period before you patched as well.
What to look at:
- Portal access logs: unusual requests from unknown IP addresses, especially with odd parameters or addresses of external servers.
- Outbound connections from the portal server to unknown internet addresses, for example over LDAP or RMI, protocols JNDI commonly uses.
- Unknown or recently created user accounts and permission changes in user management (UME).
- Unexpected changes to the portal configuration.
If you find any of this, or you have no logs from before the fix, bring in an SAP security or forensics specialist. For this flaw, CISA also points to its “Forensics Triage Requirements”. Do not reinstall a suspicious system or delete its logs, so that evidence is preserved. Disconnect it from the network instead.