CVE Tools

CVE-2026-76964

Memory Corruption Vulnerability in SAP NetWeaver AS ABAP (Internet Communication Manager)

No known exploitation. EPSS puts it in the 38th percentile. No fix published yet.

Check it yourself

OpenVAS · 1 check

e.g. OID 1.3.6.1.4.1.25623.1.0.196625

Run the check

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • SAP_SE SAP NetWeaver AS ABAPAffected: KRNL64UC 7.53Upgrade to: not statedAffected: KERNEL 7.53Upgrade to: not statedAffected: 7.54Upgrade to: not statedAffected: 7.77Upgrade to: not stated + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Ask your SAP administrator or hosting provider whether your SAP NetWeaver AS ABAP system is affected and internet-facing.
  2. Restrict or firewall access to the Internet Communication Manager (ICM) from the public internet until more is known.
  3. Check for a vendor security note or patch from SAP regularly, as none is available yet.
  4. Monitor SAP announcements and apply the official fix as soon as SAP publishes one.
  5. Ask your SAP partner if temporary mitigations (e.g., network segmentation, WAF rules) are recommended for your version.

What it is

From the CVE record

SAP NetWeaver Application Server ABAP does not sufficiently validate certain network input processed by an internal component. An unauthenticated attacker could send specially crafted network traffic to trigger a memory corruption condition in the affected functionality. Successful exploitation could allow the attacker to execute arbitrary code and fully compromise the system, resulting in a high impact on confidentiality, integrity and availability of the system.

In plain language

Written by AI from the record

This is a maximum-severity flaw in SAP NetWeaver's web-facing component that could let an outsider take over the system without logging in, but there's no sign anyone is exploiting it yet and SAP has not released a fix.

Unauthenticated remote memory corruption (CWE-1287, improper validation of specified type of input) in SAP NetWeaver AS ABAP's Internet Communication Manager allows arbitrary code execution and full compromise via crafted network traffic, with no vendor patch currently available.

If you're affected

  • Full system takeover
  • Business data exposure
  • Operational disruption
  • Ransomware risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS38th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 38th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained.

Lifecycle

7 events over 4 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updatedrecord updated
  3. Publishedweakness classified, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for SAP_SE, not every advisory.