# CVE-2026-44761: Insecure Sample Credentials in SAP Commerce Cloud

> An attacker can use publicly documented sample OAuth2 credentials to access APIs and read or modify data if the default configuration is not changed.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-7xw7-hxcm-552f

## What is CVE-2026-44761?

CVE-2026-44761 is a critical vulnerability in SAP_SE SAP Commerce Cloud, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-44761?


## How do I fix CVE-2026-44761?

No fix has been published for CVE-2026-44761 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44761 being exploited?

There is no known exploitation of CVE-2026-44761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44761 and fix it if it is affected.

What it is: CVE-2026-44761 is a critical vulnerability in SAP_SE SAP Commerce Cloud, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44761 in the wild and no public exploit code.

Affected product: SAP_SE SAP Commerce Cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44761/ (Markdown: https://insights.sbomify.com/CVE-2026-44761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44761
- OSV: https://osv.dev/vulnerability/CVE-2026-44761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44761/
Summaries are generated and may contain mistakes; the official description above is the record.