Skip to main content
Mallory
HighVulnerability

CVE-2026-44751: Missing Authorization Check in SAP Application Server ABAP Report Generation

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.
CVSS7.1High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-44751CWE-862 · Missing Authorization

CVE-2026-44751 is a missing authorization check vulnerability in SAP Application Server ABAP and ABAP Platform report generation functionality within the SAP_BASIS layer. The vulnerable code path does not perform the necessary authorization validation for an authenticated user before allowing execution of a report generation command. As a result, a low-privileged authenticated attacker can overwrite report-related information owned by another user, including executable reports or other user-associated report data. The flaw stems from the absence of the required AUTHORITY-CHECK enforcement in a sensitive ABAP operation, enabling unauthorized modification of objects that should be protected by role-based access controls.

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 allows an authenticated attacker to overwrite another user’s report-related data and achieve privilege escalation. The primary security consequence is high integrity impact because an attacker can silently alter executable reports, business logic, or report outputs in ways that may affect downstream processing or decision-making. The vulnerability also has low availability impact due to potential disruption caused by corrupted or replaced report content. No confidentiality impact has been identified.

Mitigation

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

If immediate patching is not possible, restrict access to report generation transactions and enforce least privilege for ABAP user accounts to reduce exposure. Enable and review SAP change logging and Security Audit Log monitoring to detect unauthorized report generation or modification activity. Proactive ABAP code review and scanning for missing AUTHORITY-CHECK statements can help identify similar exposure elsewhere, but these measures are compensating controls and do not replace the vendor fix.

Remediation

Patch, then assume compromise.

Apply SAP Security Note 3735546 or the corresponding fixed vendor update for affected SAP NetWeaver AS ABAP and ABAP Platform systems. The fix introduces the missing authorization checks in the affected report generation code path. Affected SAP_BASIS versions include 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 758, and 816; organizations running these versions should prioritize patching.

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-44751 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-44751 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44751?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-44751.
Is there a patch for CVE-2026-44751?
Apply SAP Security Note 3735546 or the corresponding fixed vendor update for affected SAP NetWeaver AS ABAP and ABAP Platform systems. The fix introduces the missing authorization checks in the affected report generation code path.
How severe is CVE-2026-44751?
CVE-2026-44751 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 0.21% (11th percentile) as of Sep 25, 2026.
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 activity2Community discussion across Reddit, Mastodon, and other social sources.