Skip to main content
Mallory
CriticalVulnerability

CVE-2026-44748: XML Signature Wrapping in SAP NetWeaver AS ABAP and ABAP Platform SAML Authentication

Published Jun 9, 2026 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.9Critical · v3.1
EPSS0.23%14th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-44748CWE-347 · Improper Verification of…

CVE-2026-44748 is an XML Signature Wrapping vulnerability in SAP NetWeaver Application Server ABAP and ABAP Platform, affecting SAML authentication and signed XML processing. Signature verification can validate an XML element referenced by ID while application logic processes a different, attacker-modified element. An authenticated attacker with ordinary privileges can reuse a valid signed message, relocate the signed element, and introduce tampered identity information that is accepted despite successful signature verification. Affected SAP_BASIS releases include 702, 731, 740, 750–758, 816, 918, and 919. The vulnerability has a CVSS v3.1 score of 9.9.

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 undermine SAML authentication and trust in signed identity information, enabling identity spoofing, unauthorized access to sensitive user data, and privilege escalation. Tampered identity information can also enable unauthorized actions and disruption of normal application usage. Confidentiality, integrity, and availability impacts are rated high.

Mitigation

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

Temporarily disabling SAML authentication can reduce exposure through SAML workflows, but does not address all affected signed XML use cases and is not a substitute for patching. Pending remediation, restrict access to ordinary-privilege SAP accounts, segment network access to affected ABAP systems, and monitor for unusual signed XML submissions and unexpected identity changes.

Remediation

Patch, then assume compromise.

Apply SAP Security Note 3746332, released on June 9, 2026, using the correction instructions or applicable vendor-specified updates for the installed SAP_BASIS release. The correction updates ABAP signature-verification logic to reject modified XML documents. Prioritize deployment across affected SAP NetWeaver AS ABAP and ABAP Platform systems.

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-44748 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2026-44748 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44748?
As of Nov 10, 2026, Mallory has found no public exploit for CVE-2026-44748.
Is there a patch for CVE-2026-44748?
Apply SAP Security Note 3746332, released on June 9, 2026, using the correction instructions or applicable vendor-specified updates for the installed SAP_BASIS release. The correction updates ABAP signature-verification logic to reject modified XML documents.
How severe is CVE-2026-44748?
CVE-2026-44748 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.23% (14th percentile) as of Nov 10, 2026.
Activity feed

Recent activity

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

View more in app →
+6 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 activity14Community discussion across Reddit, Mastodon, and other social sources.