Skip to main content
VulnerabilityPublished

CVE-2026-34260: SAP S/4HANA (SAP Enterprise Search for ABAP) · SQL Injection

Affects SAP S/4HANA (SAP Enterprise Search for ABAP)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
SAP_SESAP S/4HANA (SAP Enterprise Search for ABAP)Affected
  • SAP_BASIS 751 – SAP_BASIS 816
9 affected builds
Fixed in–

AI-suggested

Until an official fix is released, restrict access to the affected SAP S/4HANA components to trusted users only and monitor for suspicious activity related to SQL injection attempts. Avoid exposing the vulnerable interface to untrusted networks. Follow SAP's security recommendations once available.

Description

CVE-2026-34260 is a critical SQL injection vulnerability in SAP S/4HANA (SAP Enterprise Search for ABAP) affecting multiple SAP_BASIS versions. An authenticated attacker can inject malicious SQL commands via user-controlled input that is concatenated directly into SQL queries without proper sanitization. Successful exploitation can lead to unauthorized disclosure of sensitive database information and application crashes, impacting confidentiality and availability. Integrity is not affected. No official patch or remediation guidance is currently confirmed.

References

Community reviews

Loading reviews…