Affects widely used enterprise product (SAP Commerce Cloud). Public sample OAuth2 creds can grant token-based API access allowing broad data read/modify — high-impact for affected orgs.
CVE-2026-44761
Default sample OAuth2 client in SAP Commerce Cloud allows token issuance with public creds.
Is CVE-2026-44761 being exploited?
Not confirmed. CVE-2026-44761 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-44761?
CVE-2026-44761 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44761?
Not known from our data. No patch reference has been recorded for CVE-2026-44761, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-44761 affect?
CVE-2026-44761 affects SAP Commerce Cloud, SAP Commerce (Hybris), OAuth2 client configurations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44761?
Remove or rotate sample OAuth2 client creds, revoke tokens, audit configs and API access logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can use public sample OAuth2 credentials to obtain access tokens and read/modify data via APIs.
Immediate action required
- affectedHY_COM 2205
- affectedCOM_CLOUD 2211
- affected2211-JDK21
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.