Skip to main content
Mallory
CriticalVulnerability

CVE-2026-27681: SQL Injection in SAP Business Planning and Consolidation and SAP Business Warehouse

Published Apr 14, 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.9Critical · v3.1
EPSS0.51%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-27681CWE-89 · Improper Neutralization of Special…

CVE-2026-27681 is a critical SQL injection vulnerability affecting SAP Business Planning and Consolidation (BPC) and SAP Business Warehouse (BW). The flaw is attributed to insufficient authorization checks and unsafe handling of user-supplied input in SQL processing, allowing an authenticated user to execute crafted SQL statements. Available reporting indicates exploitation may occur through a vulnerable ABAP program that processes uploaded input and subsequently executes attacker-controlled SQL. Successful exploitation enables direct interaction with the backend database, including unauthorized reading, modification, and deletion of data. The vulnerability is rated CVSS 3.1 9.9 with vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

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 gives a low-privilege authenticated attacker the ability to execute arbitrary SQL statements in the context of the affected application’s database access. This can result in unauthorized disclosure of database contents, tampering with records, deletion of data, and service disruption. Because the vulnerability has changed scope and SAP BPC/BW deployments may share backend database infrastructure with other SAP components, the impact can extend beyond the vulnerable application to other connected modules or shared data stores, producing high confidentiality, integrity, and availability impact.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting the ability of lower-privileged users to reach the vulnerable functionality and by revoking the S_GUI authorization object with Activity 60 (Upload) from accounts that do not strictly require it. Additional defensive measures include limiting authenticated access to affected BPC/BW components, reviewing roles for least privilege, and monitoring for abnormal SQL-related activity until patches are deployed.

Remediation

Patch, then assume compromise.

Apply SAP’s security update for CVE-2026-27681 as provided in the April 14, 2026 SAP Security Patch Day fixes. Customers should use SAP Note 3719353 to determine product applicability and the correct fixed versions for their environment, then update all affected SAP Business Planning and Consolidation and SAP Business Warehouse systems accordingly.

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-27681 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-27681 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-27681?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-27681.
Is there a patch for CVE-2026-27681?
Apply SAP’s security update for CVE-2026-27681 as provided in the April 14, 2026 SAP Security Patch Day fixes. Customers should use SAP Note 3719353 to determine product applicability and the correct fixed versions for their environment, then update all affected SAP Business Planning and Consolidation and SAP Business Warehouse systems accordingly.
How severe is CVE-2026-27681?
CVE-2026-27681 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.51% (44th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
nuclei templates pull requestsNews · Apr 17, 2026[Bounty] Add 5 Nuclei templates for April 2026 CVEs (Batch 10) by eyangfeng88-arch · Pull Request #15961 · projectdiscovery/nuclei-templates · GitHubAn authenticated SQL injection vulnerability affecting SAP BPC/BW.Read more ↗cvefeed high severityNews · Apr 14, 2026CVE-2026-27681 - SQL Injection vulnerability in SAP Business Planning and Consolidation and SAP Business WarehouseAn authorization flaw in SAP Business Planning and Consolidation and SAP Business Warehouse that allows an authenticated user to execute crafted SQL statements, resulting in read, modification, and deletion of database data.Read more ↗csirt skNews · Apr 14, 2026Kritická zraniteľnosť SAP Business Planning and Consolidation a SAP Business Warehouse | CSIRT.SKCritical authorization-check flaw in SAP Business Planning and Consolidation and SAP Business Warehouse that allows a low-privileged authenticated remote attacker to inject and execute SQL commands, enabling reading, modification, and deletion of database data.Read more ↗zeropath blogNews · Apr 13, 2026Brief Summary: CVE-2026-27681 Critical SQL Injection in SAP Business Planning and Consolidation and Business Warehouse - ZeroPath Blog | ZeroPathA critical SQL injection vulnerability in SAP Business Planning and Consolidation (BPC) and SAP Business Warehouse (BW) that allows a low-privileged authenticated user to inject arbitrary SQL statements to read, modify, and delete database data.Read more ↗
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 activity14Community discussion across Reddit, Mastodon, and other social sources.