Unauthorized API access via retained sample credentials
Published Jul 14, 2026 · Updated Jul 14, 2026
Default credentials in SAP Commerce Cloud HY_COM 2205, COM_CLOUD 2211, and 2211-JDK21 allow remote attackers to obtain OAuth tokens. A sample OAuth2 client can retain the same publicly documented client ID and secret, and the token endpoint accepts them as valid credentials. Exposure requires the sample client to remain unchanged; successful token use permits API data reads and modifications but does not interrupt service.
Summary
What happened
Default credentials in SAP Commerce Cloud HY_COM 2205, COM_CLOUD 2211, and 2211-JDK21 allow remote attackers to obtain OAuth tokens. A sample OAuth2 client can retain the same publicly documented client ID and secret, and the token endpoint accepts them as valid credentials. Exposure requires the sample client to remain unchanged; successful token use permits API data reads and modifications but does not interrupt service.
The record
- CVE
- CVE-2026-44761
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- cap-js
- Product
- SAP Commerce Cloud
- Classifications
- CWE-1392, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2211-JDK21
- Affected versionversion=COM_CLOUD 2211
- Affected versionversion=HY_COM 2205
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo