CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

SAP Commerce Cloud

product · product:sap-commerce-cloud

Coverage
2
first 2026-07-14 → last 2026-10-11
Latest activity
2026-08-16
SAP's August patch day is led by a CVSS 10.0 pre-auth code-execution flaw in the Commerce Cloud Data Hub…
Peak priority
high
1 high · 1 notable
Targets
public-sector
sectors: public-sector, finance, manufacturing · regions: europe, switzerland
Sources cited
9
6 hosts

Action items (4)

Do-now tasks recorded on the entries about SAP Commerce Cloud, newest first. Check the date before acting on an older one.

  • Rebuild and redeploy the fixed release from SAP Security Note 3771065 on every self-managed SAP Commerce Cloud instance, since an installed patch is not sufficient for this component; restrict the vulnerable Data Hub Adapter endpoint with a Commerce Cloud IP filter set until the redeploy, and give any instance that stayed reachable and unredeployed after 2026-08-14 a compromise assessment.
    2026-08-12CVE-2026-58231 +5
  • For any SAP Manufacturing Integration and Intelligence instance patched with Security Note 3765948 (CVE-2026-44772), configure and maintain the new 'Secure Transformer' system property with an explicit allowed-hosts list for XSL files; the patch alone does not remove the vulnerable servlet, and without this property the flaw remains exploitable regardless of patch status.
    2026-08-12CVE-2026-58231 +5
  • Audit SAP Commerce Cloud for CVE-2026-44761: check whether the instance ever ran SAP's documented sample OAuth2 configuration and left the shipped client secret in production; if so, rotate that secret and apply SAP Note 3753495; the credential is publicly known, so patching without rotating leaves a valid attacker token.
    2026-07-14CVE-2026-44747 +2
  • Patch the unauthenticated, network-reachable SAP Approuter request-smuggling flaw (CVE-2026-27690, SAP Note 3720138) on any non-Cloud-Foundry Approuter fronting shared back-ends, and apply the NetWeaver AS ABAP kernel fix (CVE-2026-44747, SAP Note 3747367).
    2026-07-14CVE-2026-44747 +2

Defender insights

What each entry about SAP Commerce Cloud tells a defender to do, newest first.

2026-07-14NOTABLESAP patches an unauthenticated Approuter request-smuggling flaw and a Commerce Cloud public-default-credential exposure; NCSC-CH flags all three

Triage

Story timeline

  1. 2026-08-12SAP Commerce Cloud CVE-2026-58231: an unauthenticated request to a vulnerable Data Hub Adapter endpoint reaches arbitrary code execution (CVSS 10.0), and the fix needs a rebuild and redeploy
    trending-vulnerabilitiesSAP's August patch day is led by a CVSS 10.0 pre-auth code-execution flaw in the Commerce Cloud Data Hub Adapter, fixed only by a rebuild and redeploy
  2. 2026-07-14SAP July 2026 Security Patch Day: three CVSS ≥9.1 flaws in NetWeaver AS ABAP, Approuter and Commerce Cloud, two reachable without authentication
    trending-vulnerabilitiesSAP patches an unauthenticated Approuter request-smuggling flaw and a Commerce Cloud public-default-credential exposure; NCSC-CH flags all three

Hunting pivots

CVEs
CVE-2026-27690CVE-2026-34265CVE-2026-42945CVE-2026-44747CVE-2026-44758CVE-2026-44761CVE-2026-44772CVE-2026-58231CVE-2026-58243
Releases covered
SAP Commerce Cloud ×2
Tags
patch-available ×2pre-auth ×2vulnerabilities ×2auth-bypassinfo-disclosurerce
ATT&CK techniques (4 across 6 tactics)

4 techniques observed across 2 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessValid Accounts: Default Accounts · Exploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter
  • PersistenceValid Accounts: Default Accounts
  • Privilege EscalationValid Accounts: Default Accounts
  • StealthValid Accounts: Default Accounts
  • Credential AccessUnsecured Credentials: Credentials In Files

Initial Access TA0001

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · ATT&CK page ↗

T1190Exploit Public-Facing Application×2

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · 2026-07-14/sap-july-2026-patch-day-netweaver-approuter-commerce-cloud · ATT&CK page ↗

Execution TA0002

T1059Command and Scripting Interpreter×1

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · ATT&CK page ↗

Persistence TA0003

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · ATT&CK page ↗

Privilege Escalation TA0004

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · ATT&CK page ↗

Stealth TA0005

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-12/sap-august-2026-cve-2026-58231-commerce-cloud-data-hub-rce · ATT&CK page ↗

Credential Access TA0006

T1552.001Unsecured Credentials: Credentials In Files×1

Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.

Evidence: 2026-07-14/sap-july-2026-patch-day-netweaver-approuter-commerce-cloud · ATT&CK page ↗

Entries about SAP Commerce Cloud (2)

2026-08-12 · view entry permalink →

HIGHCVE-2026-58231 +5updatedNATOA1

SAP Commerce Cloud CVE-2026-58231: an unauthenticated request to a vulnerable Data Hub Adapter endpoint reaches arbitrary code execution (CVSS 10.0), and the fix needs a rebuild and redeploy

SAP's August 2026 Security Patch Day of 2026-08-11 released 28 new security notes plus one GitHub security advisory, with two updates to previously released notes (SAP SE, 2026-08-11); Onapsis, counting the cycle its own way, puts it at thirty-three notes including five HotNews and nine High Priority (Onapsis Research Labs, 2026-08-11). The one that changes an exposure picture rather than a patch schedule is CVE-2026-58231, carried by SAP Security Note 3771065 at CVSS 10.0: an improper-authorization flaw in the Data Hub Adapter of SAP Commerce Cloud. Onapsis, which worked with SAP on eleven of the notes in this cycle, describes the cause as insufficient authorization checks combined with insufficient input validation, and the outcome as arbitrary code execution with compromise of internal components (Onapsis Research Labs, 2026-08-11). The reason this ranks above a routine critical: Commerce Cloud runs online stores, so in analyst judgement the vulnerable component is likely to be reachable from the internet, and the score's pre-auth, no-interaction profile means reaching it takes a crafted request rather than a foothold.

Remediation for this one is not a patch install. Onapsis states customers must patch to the fixed Commerce Cloud release levels referenced in the note and then rebuild and redeploy the updated version, and that the interim exposure reduction available today is an IP filter set restricting access to the vulnerable endpoint (Onapsis Research Labs, 2026-08-11). Any organisation whose change process treats "SAP note applied" as equivalent to "fixed" will record this as remediated while the storefront is still reachable. SAP Security Note 3773203 is SAP's fix for CVE-2026-42945 (CVSS 8.1) as a potential buffer overflow affecting Commerce Cloud public-cloud deployments with NGINX (SAP SE, 2026-08-11), and it is consumed the same way, by building and deploying the Commerce Cloud application (Onapsis, 2026-08-11).

Further notes Onapsis classes as HotNews matter to different estates. CVE-2026-44772 (CVSS 9.9, Note 3765948) and CVE-2026-44758 (CVSS 9.1, Note 3758900) are code-injection flaws in SAP Manufacturing Integration and Intelligence reaching arbitrary command execution on the underlying host; Onapsis states the lower score on the second reflects a higher privilege requirement. The two remedies are not the same: for Note 3758900 (CVE-2026-44758) the patch removes the vulnerable servlet component outright, while for Note 3765948 (CVE-2026-44772) the servlet stays in place and customers must additionally configure and maintain a new "Secure Transformer" system property naming the hosts allowed to serve XSL files to it (Onapsis Research Labs, 2026-08-11). CVE-2026-34265 (CVSS 9.8, Note 3714806) is, in analyst judgement, the one to weigh against internal network exposure rather than internet exposure. Onapsis describes it: "Logical errors in DIAG protocol parsing allow an unauthenticated attacker to generate memory corruptions" in the Application Server ABAP kernel, with potential disclosure of sensitive system information or a crash of the instance (Onapsis Research Labs, 2026-08-11). The affected kernel list spans KRNL64NUC/KRNL64UC and KERNEL builds from 7.22 through 9.19 (SAP SE, 2026-08-11); since DIAG is the SAP GUI presentation protocol, the affected listener is, in analyst judgement, one that ordinarily faces user workstations. Rounding out the High Priority set, CVE-2026-58243 (CVSS 8.8, Note 3772411) covers the SQL Console in SAP ABAP Developer Tools, where support for host expressions inside SQL statements let a low-privileged authenticated user run database operations they should not reach (Onapsis Research Labs, 2026-08-11).

On patch day NCSC-CH rated the exploitation status unknown (NCSC-CH, 2026-08-11); three days later Defused reported exploitation attempts against the Data Hub Adapter flaw at its honeypots (BleepingComputer, 2026-08-14), and on 2026-08-15 NCSC-NL relayed Defused's report of attackers actively scanning for vulnerable systems (NCSC-NL, 2026-08-15). The Data Hub Adapter flaw demands action ahead of the normal SAP patch cadence: it is an unauthenticated, no-interaction path to code execution, disclosed with a CVSS 10.0 and a documented interim network control. Detection concepts are ordinary but specific: in web and reverse-proxy access logs, surface requests to the Data Hub Adapter endpoint from source addresses outside the integration ranges that legitimately feed it, and treat any such request that precedes an unexplained child process under the Commerce Cloud application account as an incident rather than an anomaly. In analyst judgement, legitimate Data Hub imports come from a known set of integration sources, so the source address and the calling identity, not the request body, are the useful filter. On the ABAP side, Onapsis names a crash of the instance among the possible outcomes (Onapsis Research Labs, 2026-08-11); in analyst judgement, a DIAG-parsing memory-corruption attempt would therefore surface as work-process crashes or short dumps clustered on one instance rather than as an authentication event.

Logical errors in DIAG protocol parsing allow an unauthenticated attacker to generate memory corruptions.

As a temporary workaround, customers can reduce their exposure by configuring an IP Filter Set in SAP Commerce Cloud to restrict access to the vulnerable endpoint.

Onapsis Research Labs 2026-08-11

First exploitation attempts against CVE-2026-58231 (unauth RCE in SAP Commerce Cloud, CVSS 10.0) is now hitting our honeypots - 3 days after patch day,

Defused, quoted by BleepingComputer

Security firm Defused reports that malicious actors are actively scanning and searching for vulnerable Data Hub Adapter systems. (translated from Dutch)

NCSC-NL

SAP Commerce Cloud allows an unauthenticated attacker to abuse a default authentication client and submit specially crafted input to certain functions lacking sufficient validation

SAP, quoted by BleepingComputer
Updaterun 2026-08-16T0411Z-intelactionscvesevidencesourcestagstechniquesbody

The Commerce Cloud flaw, which carried no reported exploitation at the 2026-08-11 patch day, is being attacked. Threat-intelligence firm Defused reported on 2026-08-14 that the first exploitation attempts against CVE-2026-58231 were arriving at its honeypot sensors three days after SAP's 2026-08-11 patch day, and stated in the same report that the vulnerability has no public proof-of-concept (BleepingComputer, 2026-08-14). Those two facts together are the operationally interesting part: in analyst judgement, whoever is sending these requests developed exploitation attempts without published research to copy, on a three-day clock, against a component whose remediation is slower than a patch install. On 2026-08-15 the Dutch national cyber security centre published advisory NCSC-2026-0302, which records that attackers are actively scanning for and seeking out vulnerable Data Hub Adapter systems (NCSC-NL, 2026-08-15).

The mechanism is worth restating precisely because it shapes what an exposed request looks like: SAP describes the flaw as allowing an unauthenticated attacker to abuse a default authentication client and submit specially crafted input to functions that lack sufficient validation, reaching arbitrary code execution (BleepingComputer, 2026-08-14). The exposure is real rather than theoretical: Shadowserver tracks over 4,200 IP addresses carrying a SAP Commerce Cloud fingerprint, most of them in Europe and North America, though the same reporting is explicit that it cannot say how many of those are honeypots or already remediated (BleepingComputer, 2026-08-14).

Calibrate the status honestly. What is confirmed is exploitation attempts against sensors (BleepingComputer, 2026-08-14) and scanning for vulnerable systems (NCSC-NL, 2026-08-15); no party reports a compromised production instance, and SAP has not flagged the flaw as exploited in its own advisory (BleepingComputer, 2026-08-14). That distinction matters for triage effort, not for patch priority: exploitation attempts appeared within days of a public fix on this component, and the remediation is a rebuild-and-redeploy cycle measured in change windows.

Detection, in vendor-neutral terms: in web-access and application logs for the Data Hub Adapter, look for unauthenticated requests to the adapter's functions that present the default authentication client rather than a customer-provisioned one, and, in analyst judgement, for adapter activity that no scheduled integration run accounts for. Pair that with egress review from the Commerce Cloud application tier, since arbitrary code execution there runs inside the storefront's own host. Hardening remains the vendor's own path: Onapsis, which works with SAP on its patch cycle, records that customers must patch to the fixed Commerce Cloud release levels referenced in the note and then re-build and re-deploy the updated version, and that configuring an IP Filter Set in Commerce Cloud to restrict access to the vulnerable endpoint is the temporary workaround that reduces exposure meanwhile (Onapsis, 2026-08-11).

Correctionrun 2026-08-28T0409Z-intelcvesbody

The entry stated that SAP's fix "removes the vulnerable servlet component in both cases" for CVE-2026-44772 (Note 3765948) and CVE-2026-44758 (Note 3758900). Onapsis's own text supports that statement for only one of the two. For Note 3758900 the patch does remove the vulnerable servlet component outright (Onapsis Research Labs, 2026-08-11). For Note 3765948 (CVE-2026-44772, CVSS 9.9) the servlet stays in place, and Onapsis states the required remedy directly: "After implementing the patch, customers need to maintain the new system property 'Secure Transformer' with a list of allowed hosts for hosting XSL files. Only XSL files from these hosts can be consumed by the vulnerable servlet" (Onapsis Research Labs, 2026-08-11).

The practical consequence: an SAP Basis team that applied Note 3765948 and recorded the CVSS 9.9 flaw as remediated, without configuring the Secure Transformer allowed-hosts property, has left the vulnerable servlet reachable; the patch alone does not close the flaw for this note. Teams that patched CVE-2026-44772 should verify the Secure Transformer property is now configured with an explicit allowed-hosts list, not merely that Note 3765948 shows as applied. Nothing about Note 3758900 (CVE-2026-44758) or any other flaw in this entry changes.

Correctionrun 2026-10-11T1307Z-auditsummaryreferencesbodyevidenceactionstitlecvestags

SAP Security Note 3773203 addresses CVE-2026-42945 in Commerce Cloud public-cloud deployments with NGINX (SAP SE, 2026-08-11); Onapsis states that the fix reaches customers when they build and deploy their Commerce Cloud applications (Onapsis, 2026-08-11). No cited source calls the vulnerable endpoint an import endpoint; SAP describes crafted input to functions that lack sufficient validation (BleepingComputer, 2026-08-14), and Onapsis names the vulnerable endpoint without naming its function (Onapsis Research Labs, 2026-08-11). On patch day NCSC-CH rated the exploitation status unknown (NCSC-CH, 2026-08-11). The status of CVE-2026-58231 no longer reads exploited: what is reported is exploitation attempts against Defused's honeypots and no compromised production instance (BleepingComputer, 2026-08-14), plus Defused's report of active scanning, which NCSC-NL relays (NCSC-NL, 2026-08-15).

Builds on: CVE-2026-42945, NGINX Open Source / Plus / F5 WAF products: 18-year-old heap buffer overflow in…

vulnerability12 Aug 04:45Zmulti-sourceOpen finding →
Sources: SAP SE (Security Patch Day) · Onapsis Research Labs · NCSC Switzerland, Cyber Security Hub · NCSC-NL (Nationaal Cyber Security Centrum) · BleepingComputer

2026-07-14 · view entry permalink →

NOTABLECVE-2026-44747 +2NATOB1

SAP July 2026 Security Patch Day: three CVSS ≥9.1 flaws in NetWeaver AS ABAP, Approuter and Commerce Cloud, two reachable without authentication

SAP's July 2026 Security Patch Day (14 July) carries three critical flaws NCSC Switzerland's Cyber Security Hub relayed directly to Swiss constituents, none with reported exploitation at publication (NCSC-CH, 2026-07-14; Onapsis Research Labs, 2026-07-14). CVE-2026-44747 (CVSS 9.9) is a memory-corruption flaw in the SAP NetWeaver Application Server ABAP kernel; SecurityWeek characterises successful exploitation as allowing an attacker to access and modify data and cause system unavailability, and SAP's only interim workaround (disabling the affected ICF nodes) is impractical because it breaks SAP GUI for HTML, so patching the kernel is the real mitigation (SecurityWeek, 2026-07-14). CVE-2026-27690 (CVSS 9.1) is an HTTP request-smuggling flaw in SAP Approuter's non-Cloud-Foundry deployments: an unauthenticated request desynchronises the request/response stream on a shared front-end, a primitive usable to poison or hijack another user's request. CVE-2026-44761 (CVSS 9.1) is a hardcoded sample OAuth2 credential in SAP Commerce Cloud; any customer that ran SAP's own documented sample configuration and never rotated the shipped secret exposes a publicly-known credential an unauthenticated attacker can use to obtain a valid OCC-API access token (Onapsis Research Labs, 2026-07-14).

The vulnerability affects SAP Approuter deployments in non-Cloud Foundry environments and allows an unauthenticated attacker to send a specially crafted HTTP request that leads to request-response desynchronization.

Exploitation requires that the customer execute the sample script and retain the resulting OAuth2 client in production without replacing the hardcoded secret.

Successful exploitation of the security defect could allow an attacker to access and modify data, and cause system unavailability, SAP security firm Onapsis explains.

SecurityWeek 2026-07-14
vulnerability14 Jul 20:19Zmulti-sourceOpen finding →
Sources: Onapsis Research Labs · NCSC Switzerland, Cyber Security Hub · SecurityWeek · SAP Support Portal

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns2

Source distribution

  • onapsis.com2 (22%)
  • security-hub.ncsc.admin.ch2 (22%)
  • support.sap.com2 (22%)
  • advisories.ncsc.nl1 (11%)
  • bleepingcomputer.com1 (11%)
  • securityweek.com1 (11%)
All cited sources (9)