VulnerabilityPublished 10 Feb 2026

CVE-2026-24321: SAP Commerce Cloud · Exposure of Private Personal Information to an Unauthorized Actor

Affects SAP Commerce CloudSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SESAP Commerce Cloud	Affected =2211-JDK21	Fixed in–

AI-suggested

European organizations should immediately audit their SAP Commerce Cloud deployments to identify exposed API endpoints accessible without authentication. Implement strict access control mechanisms to ensure all sensitive API endpoints require proper authentication and authorization. Employ API gateways or web application firewalls (WAFs) to monitor and restrict suspicious API traffic. Regularly update SAP Commerce Cloud to the latest patched versions once SAP releases fixes addressing this vulnerability. Conduct thorough penetration testing focused on API security to detect similar exposure issues. Implement logging and alerting for unusual API access patterns to enable rapid incident response. Review and minimize the amount of personal data accessible through APIs, applying the principle of least privilege. Additionally, organizations should review their data protection policies and ensure compliance with GDPR requirements regarding personal data exposure and breach notification.

Description

CVE-2026-24321 is a medium-severity vulnerability in SAP Commerce Cloud that allows unauthenticated users to access multiple API endpoints exposing sensitive personal information. The flaw stems from improperly secured APIs that do not require authentication, enabling attackers to retrieve data not intended for public access. While the vulnerability impacts confidentiality, it does not affect data integrity or system availability. The CVSS score of 5.3 reflects the ease of exploitation without authentication and the limited confidentiality impact. No known exploits are currently reported in the wild. European organizations using affected SAP Commerce Cloud versions (HY_COM 2205, COM_CLOUD 2211, 2211-JDK21) should prioritize reviewing API exposure and applying vendor patches or mitigations once available. Countries with significant SAP Commerce Cloud deployments and critical e-commerce infrastructure are at higher risk. Mitigation should focus on restricting API access, implementing strong authentication, and monitoring for unusual API requests.

Impact

For European organizations, the exposure of private personal information through SAP Commerce Cloud APIs can lead to significant privacy breaches, potentially violating GDPR and other data protection regulations. Even though the impact on confidentiality is rated as low, unauthorized access to personal data can result in reputational damage, regulatory fines, and loss of customer trust. Since SAP Commerce Cloud is used by many enterprises for online retail and customer management, the leakage of sensitive customer data could affect business operations and customer relationships. The lack of impact on integrity and availability means that system operations remain stable, but the confidentiality breach alone is critical in the context of stringent European data privacy laws. Organizations in sectors such as retail, finance, and telecommunications that rely on SAP Commerce Cloud are particularly vulnerable. The potential for automated exploitation without authentication increases the risk of mass data harvesting by malicious actors.

Summary

CVE-2026-24321 is a vulnerability identified in SAP Commerce Cloud, specifically affecting versions HY_COM 2205, COM_CLOUD 2211, and 2211-JDK21. The issue arises because multiple API endpoints are exposed to unauthenticated users, allowing them to submit requests and retrieve sensitive personal information that should not be publicly accessible. This vulnerability is classified under CWE-359, which pertains to the exposure of private information to unauthorized actors. The technical root cause is the lack of proper access controls on certain API endpoints, which bypass authentication and authorization checks. The vulnerability has a CVSS v3.1 base score of 5.3, indicating a medium severity level. The vector string (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) shows that the attack can be performed remotely over the network without any privileges or user interaction, impacting confidentiality only. There is no impact on integrity or availability, which limits the overall damage. No patches or exploits are currently reported, but the exposure of personal data can lead to privacy violations and regulatory non-compliance. The vulnerability affects the confidentiality of personal data processed or stored by SAP Commerce Cloud, which is widely used in e-commerce platforms globally. The issue requires immediate attention to prevent unauthorized data disclosure.

CWE-359Exposure of Private Personal Information to an Unauthorized Actor (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
Requirements
Identify and consult all relevant regulations for personal privacy. An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles.
Architecture and Design
Carefully evaluate how secure design may interfere with privacy, and vice versa. Security and privacy concerns often seem to compete with each other. From a security perspective, all important operations should be recorded so that any anomalous activity can later be identified.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V10.2.1 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Evercookie (opens in a new tab)
Cross Site Identification (opens in a new tab)
Probe iOS Screenshots (opens in a new tab)
Shoulder Surfing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:38 UTC

WeaknessesCWE-359

Technical details

References

Community reviews

Related threats