CVE-2026-44761
Insecure Sample Credentials in SAP Commerce Cloud
Description
SAP Commerce Cloud could retain a sample OAuth2 client with publicly documented sample credentials originating from sample configuration provided in SAP Help Portal documentation. If left unchanged, an unauthenticated attacker could use these well-known credentials to obtain a valid access token and invoke certain APIs to read and modify data. Successful exploitation results in high impact on confidentiality and integrity, with no impact on availability.
INFO
Published Date :
July 14, 2026, 1:16 a.m.
Last Modified :
July 14, 2026, 1:16 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | e4686d1a-f260-4930-ac4c-2f5c992778dd | ||||
| CVSS 3.1 | CRITICAL | [email protected] |
Solution
- Remove the default OAuth2 client sample.
- Configure unique and strong client credentials.
- Restrict access to sensitive APIs.
- Review all client configurations.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-44761.
| URL | Resource |
|---|---|
| https://me.sap.com/notes/3753495 | |
| https://url.sap/sapsecuritypatchday |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-44761 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-44761
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-44761 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-44761 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Jul. 14, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'SAP_SE', 'product': 'SAP Commerce Cloud', 'versions': [{'status': 'affected', 'version': 'HY_COM 2205'}, {'status': 'affected', 'version': 'COM_CLOUD 2211'}, {'status': 'affected', 'version': '2211-JDK21'}], 'defaultStatus': 'unaffected'}] Added Description SAP Commerce Cloud could retain a sample OAuth2 client with publicly documented sample credentials originating from sample configuration provided in SAP Help Portal documentation. If left unchanged, an unauthenticated attacker could use these well-known credentials to obtain a valid access token and invoke certain APIs to read and modify data. Successful exploitation results in high impact on confidentiality and integrity, with no impact on availability. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-1392 Added Reference https://me.sap.com/notes/3753495 Added Reference https://url.sap/sapsecuritypatchday