Skip to main content
Mallory
CriticalVulnerability

CVE-2026-27671: Unauthenticated RFC Memory Corruption in SAP Kernel for Application Server ABAP

Published Jun 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.44%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-27671CWE-121 · Stack-based Buffer Overflow

CVE-2026-27671 is a critical memory corruption vulnerability in the SAP Kernel used by Application Server ABAP in SAP NetWeaver and ABAP Platform. The flaw is caused by improper validation of RFC protocol data. An unauthenticated remote attacker can send a specially crafted RFC request that triggers logical errors in memory management; available reporting further characterizes the issue as a stack-based buffer overflow in the RFC protocol handler caused by insufficient bounds checking on incoming RFC data written into a stack-allocated buffer. Successful exploitation can corrupt process memory and may affect the core kernel layer shared by vulnerable ABAP application server instances.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause high impact to confidentiality, integrity, and availability. Reported outcomes include application crash or service disruption, memory disclosure, unauthorized access to sensitive data, data manipulation, and potentially arbitrary code execution through corruption of adjacent stack memory and control-flow data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of RFC-reachable services by restricting network access to trusted hosts and administrative paths only, and minimize external reachability of Application Server ABAP RFC listeners. Monitor SAP systems for anomalous or malformed RFC traffic and unexpected crashes, but these measures are compensating controls only and do not eliminate the vulnerability.

Remediation

Patch, then assume compromise.

Apply the SAP security update associated with SAP Security Note 3717897 and upgrade affected SAP Kernel versions to the vendor-specified fixed patch levels. Remediation should be prioritized across all vulnerable SAP NetWeaver AS ABAP and ABAP Platform systems, as the flaw resides in the shared SAP Kernel layer.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-27671 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-27671 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-27671?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-27671.
Is there a patch for CVE-2026-27671?
Apply the SAP security update associated with SAP Security Note 3717897 and upgrade affected SAP Kernel versions to the vendor-specified fixed patch levels. Remediation should be prioritized across all vulnerable SAP NetWeaver AS ABAP and ABAP Platform systems, as the flaw resides in the shared SAP Kernel layer.
How severe is CVE-2026-27671?
CVE-2026-27671 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.44% (38th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity12Community discussion across Reddit, Mastodon, and other social sources.