basicsecurity.net
Proof, not just disclosure.
Threats / SAP / CVE-2025-42884
CVE-2025-42884 · EUVD no mirror located · GCVE no mirror located Checked against CISA KEV on 21 Nov 2026

SAP NetWeaver vulnerability

SAP NetWeaver Enterprise Portal contains an improper neutralization of special elements in data query logic vulnerability that allows an unauthenticated attacker to disclose or modify server information via injected JNDI environment propert

Verdict

Today item — known-exploited.

Listed in CISA KEV. Prioritize remediation now and verify exposure.

CISA KEV Yes · 2026-11-205EPSS 0.00276 (verify live)6CVSS 6.53CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4

Is it exploitable?

the evidence, ranked above the score
Reported exploitation
1 independent public report of exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Known-exploited (CISA KEV)
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-11-20).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00276 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) · Affected: SAP, NetWeaver. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
CVE.org ↗Reported
Weakness (CWE)
Mapped to CWE-943 CWE-943.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CVE.org ↗Reported
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
CISA-ADP ↗Reported
Currency of the record
CISA added this to its KEV catalog 374 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

Who’s exploiting it?

attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

the attack path, told twice: adversary, then board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

What to do

defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CVSS 6.5 — CNA-assigned (CVE.org)
  • CISA SSVC triage disposition (CVE.org ADP)
  • CWE weakness mapping — CNA-assigned (CVE.org)
  • Catalogued by sap (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder is named in the public CVE record — attribution scoped to the sources checked.
  • Attacker/business narrative framing pending triage.
  • Disclosure & credit2
    Catalogued by sapCNA
    Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
    Found an error? Propose a correction.

    A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

    Corrections must cite a source.

    Paste into your Nostr client; it will sign with your key and publish.