CVE-2026-44761 is a critical authentication weakness in SAP Commerce Cloud caused by retention of a sample OAuth2 client configured with publicly documented sample credentials originating from SAP sample configuration. In affected deployments, if the sample OAuth2 client remains present and its credentials are left unchanged, an unauthenticated attacker can authenticate using those well-known credentials, obtain a valid OAuth2 access token, and invoke exposed APIs. The flaw affects SAP Commerce Cloud releases HY_COM 2205, COM_CLOUD 2211, and 2211-JDK21. The issue is classified as a hardcoded or insecure sample credential problem and is associated with CWE-1392.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical hardcoded credential vulnerability in SAP Commerce Cloud tied to sample OAuth2 client configuration scripts, which could allow unauthenticated attackers to obtain access tokens and read or tamper with system data.
A critical insecure sample credentials vulnerability in SAP Commerce Cloud that could enable unauthorized access due to default, exposed, or inadequately protected credentials.
A critical vulnerability in SAP Commerce Cloud caused by insecure sample credentials that may enable unauthorized access to affected environments.
An authentication/credential exposure vulnerability in SAP Commerce Cloud where sample OAuth2 client credentials may remain unchanged, allowing an unauthenticated attacker to obtain a valid access token and read or modify data via certain APIs.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.