CISA added CVE-2025-42884 on November 20, 2026 for SAP NetWeaver Enterprise Portal—an unauthenticated JNDI injection (CWE-943). SAP Note 3660969 (November 2025 patch day) describes parameter validation fixes; SAP states no workaround. CISA sets due date November 23, 2026.
Teams running Java AS portals that coding agents wire into SSO or employee-facing flows should treat this as server-side trust-boundary news, not a front-end XSS cleanup.
If your agent vulnerability digest skipped this note because the CVE id says 2025, reconfigure the digest to prioritize KEV add date instead of numeric year—otherwise automation will repeat the miss on the next delayed exploitation listing.
TL;DR
| Question | Answer |
|---|---|
| Exploited? | Yes — KEV 2026-11-20 |
| Affected | Enterprise Portal EP-BASIS / EP-RUNTIME 7.50 (per Note 3660969 summaries) |
| Fix | SAP Note 3660969 |
| Workaround? | None per SAP |
| Federal forensics? | No on CISA row |
| Agent angle? | Validate JNDI/portal properties agents commit |
Mechanism step by step
From SAP Note 3660969 and SAP Patch Day November 2025 summaries mirrored in EUVD-2025-60994:
- Enterprise Portal handles HTTP requests that trigger JNDI lookups (naming/directory services).
- An unauthenticated remote client supplies JNDI environment properties or a lookup URL that is not properly neutralized.
- The server performs lookup against an attacker-controlled provider, which can return crafted responses.
- Impact is disclosure or modification of server information; availability is not impacted per SAP severity text.
JNDI injection in Java portals is a familiar pattern: lookup input becomes outbound network trust. The KEV listing signals in-the-wild use beyond lab proofs.
Who is affected and how to patch
| Item | Detail |
|---|---|
| Component | EP-PIN-APF-CAT (Enterprise Portal catalog area) |
| Versions cited | EP-BASIS 7.50, EP-RUNTIME 7.50 |
| Correction | Note 3660969 — request parameters validated to block injection |
| Release train | SAP Security Patch Day — November 2025 |
Apply through SAP Support Portal with your S-user. Agents should not auto-apply SAP notes without a human change ticket—wrong note order can break portal dependencies.
Verify:
- System SP stack and EP component levels in SAP Solution Manager or
sapcontroloutputs your runbook defines. - After import, run SAP's note implementation tool checks your team already uses for Java stacks.
What this means if you run AI coding agents
SAP portals sit behind many employee SSO flows. Agents touch them when:
- Generating
web.xml/ Spring property files for portal extensions - Writing Groovy or portal PAR deployment scripts
- Documenting JNDI datasource URLs for "connect SAP to our app"
Concrete controls:
- Deny agent commits that add
java.naming.provider.urlor LDAP URLs from untrusted tickets. - Monitor egress from NetWeaver Java to 389/636/1099 after portal releases agents ship.
- Cross-check EU AI Act logging expectations if agents both patch portals and log employee data flows.
Beam observes agent shell and file edits on developer machines. It does not inspect SAP NetWeaver servers. Use it to catch agents exporting S-user passwords or curling portal admin URLs locally—not as an SAP patch orchestrator.
Why CISA listed a CVSS 6.5 flaw
KEV is exploitation-driven, not CVSS-only. Portal information disclosure and integrity bugs become staging points for lateral movement into ERP identity. Pair this with VMware vCenter KEV if agents automate dual stacks (virtualization + Java portal).
SAP Note 3660969 in change-management terms
SAP corrections arrive as Support Notes, not generic apt upgrade. For agents assisting BASIS teams:
- Download Note 3660969 from me.sap.com with customer entitlements.
- Use SPAM/SAINT or your SUM workflow—do not let agents run undisclosed
jarreplacements. - Import during a window that accounts for Portal downtime—employees lose landing pages during deployment.
- Run SAP's post-implementation verification transactions your organization already documents.
Agents excel at generating runbook YAML; they are weak at note prerequisite chains. Require human sign-off when a model conflates EP-BASIS with unrelated ABAP kernel notes.
JNDI injection mechanics (Java portal angle)
JNDI lets Java apps resolve names to objects (datasources, LDAP, RMI stubs). When portal code calls Context.lookup() with attacker-influenced URLs or environment properties:
- Attacker sends crafted HTTP request to an Enterprise Portal endpoint.
- Portal code builds a JNDI InitialContext using those inputs.
- Server opens a connection to attacker LDAP/RMI/CORBA endpoint.
- Malicious directory entries return objects that deserialize or redirect trust into disclosure paths.
SAP's fix statement—"request parameters are now properly validated"—implies allowlisting or strict parsing on provider URLs and environment keys. Without SAP's private note text, defenders should still monitor for egress to unexpected naming services.
Indicators and hunting (from public CVE text)
Public descriptions (EUVD, GHSA) suggest watching for:
- HTTP parameters containing
ldap://,ldaps://,rmi://,iiop:// java.naming.provider.urlappearing in query strings portal apps should never log- Unexpected LDAP bind attempts from NetWeaver Java PIDs to internet IPs
- Stack traces referencing
javax.naming.InitialContextin defaultTrace during portal requests
None of these are SAP-specific hunting recipes from SAP Note 3660969; they are generic signals from public CVE text for AS Java portals.
CVSS 6.5 but KEV-listed: how to prioritize
Medium scores tempt deprioritization. KEV signals observed abuse. For agent triage bots that sort only by CVSS:
- Override with KEV flag when present
- Elevate when portal is internet-facing employee SSO
- Pair confidentiality impact with phishing follow-up—disclosed server metadata feeds spear phish against SAP teams
This is the same prioritization lesson as Mongoose query injection: logic bugs below 9.0 can still be stage-one holes.
Agent integrations that accidentally widen JNDI trust
| Scenario | What to audit |
|---|---|
| Agent adds custom PAR with JNDI refs | Portal may honor new URLs without review |
| Properties file pasted from Chat UI | Hidden provider.url keys |
| Kubernetes ConfigMap mounted into NetWeaver | Shared between dev/stage with prod-like URLs |
| Automated RFC tests hitting portal | May trigger lookup code paths |
Introduce a repo hook (human or Beam advisory) that blocks commits adding naming properties unless tied to an approved ticket number.
November 2025 vs KEV November 2026 (timeline)
SAP published Note 3660969 on the November 2025 Patch Day (CVE dated in the 2025 series). CISA's KEV add November 20, 2026 indicates exploitation caught up to a flaw already documented for SAP customers—teams that deferred Java portal maintenance for a year are now in federal emergency territory. Agents summarizing "old CVE" from calendar year alone should be corrected: KEV freshness drives priority, not CVE id year.
Disclosure and modification impact (SAP wording)
SAP rates confidentiality and integrity low with no availability impact—meaning service stays up while metadata shifts or leaks. For coding agents automating employee portals, subtle integrity changes (malicious portlet URLs, altered JNDI-fed labels) may evade uptime monitors. Schedule content integrity checks after patching, not only smoke login tests.
Integration with broader agent-security program
Combine portal patching with:
- EU AI Act logging if agents touch employee data flows post-patch verification
- PromptArmor frontier agent benchmarks awareness—portal XSS chains are a different class, but the same teams often own Java surfaces
- Monthly attacks tracker context when Bell-style telecom metadata appears in unrelated staging leaks
Beam's local-first posture helps prove agent operators did not export SAP support credentials during panic patching—it does not replace Note 3660969 import.
Reader checklist for BASIS and agent owners
- Confirm EP-PIN-APF-CAT component level matches Note 3660969 prerequisites.
- Open SAP Security Patch Day November 2025 entry and verify 3660969 is implemented in SPAM logs.
- Block agent PRs that add JNDI URLs until note is confirmed.
- Capture defaultTrace snapshots before and after import for diffing naming errors.
- Run employee portal smoke tests (login, portlet load, search) post-patch.
- Hunt egress LDAP for 72 hours on application servers.
- Update internal CVE wiki with KEV due 2026-11-23 even though SAP note is 2025-dated.
Closing operational note
Enterprise Portal bugs sit at the intersection of employee trust and Java enterprise cruft. Unlike a flashy ransomware headline, JNDI injection sounds abstract until you map it to directory data leaving the building or portlet integrity changing silently. SAP's medium CVSS score reflects limited availability impact, not low business risk—especially when portal pages host links to payroll, travel, and ITSM tickets.
Organizations that let coding agents generate portal extensions should treat those agents as supply-chain authors: every PAR file is code running beside naming lookups. Introduce manual code review for portal deployments even when the agent "only scaffolded" the project. SAP's parameter validation fix in Note 3660969 closes a specific code path, but custom components your agents added may still perform unsafe lookups elsewhere—hunt those independently.
For multinational teams, remember SAP portals often integrate multiple languages and themes cloned from production. An agent copying portal properties between regions can accidentally replicate vulnerable JNDI URLs into a newly internet-exposed sandbox. Standardize property templates without live provider URLs, and inject real URLs only via deployment secrets managed outside git.
When this CVE appears in agent-generated risk reports, ensure the model cites KEV status and Note 3660969, not generic "update SAP" guidance. Specific notes beat blanket advice because BASIS teams distrust vague LLM output—and distrust slows the very patching KEV tries to accelerate.
Add a calendar reminder for 2026-11-23 even if you are not federal: partners may demand attestation that Enterprise Portal nodes ingested 3660969 before renewing B2B VPNs or managed service contracts. Capture before/after SNOTE status screenshots so auditors can trace the fix without reopening SPAM logs during agent-driven refactors later in the year.
Frequently asked questions
What is SAP NetWeaver Enterprise Portal?
The Java portal front end for NetWeaver—often where employees hit apps and SSO landing pages.
Is authentication required to exploit CVE-2025-42884?
No — unauthenticated per SAP advisory text.
Where is the official fix documented?
SAP Note 3660969 and Patch Day 2025.
Related reading
- VMware vCenter KEV bypass
- Apache Roller XML-RPC KEV
- CVE volume and agent triage
- Oblomovka on agent capabilities
Primary sources: SAP Note 3660969, SAP Security Patch Day, CISA KEV, GHSA-gpv6-m7fj-wr5v
Note numbers and CISA metadata reflect publications as of November 20, 2026.

