CVE-2026-24326VulnerabilityPublished 10 Feb 2026

CVE-2026-24326: SAP S/4HANA Defense & Security (Disconnected Operations) · Missing Authorization

Affects SAP S/4HANA Defense & Security (Disconnected Operations)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 2026-10-25.

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 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 S/4HANA Defense & Security (Disconnected Operations)	Affected =603 =604 =605 =606 =616 =617 =618 =619 =800 =801 =802 =803 =804 =805 =806 =807 =808 =809	Fixed in–

AI-suggested

1. Immediately review and tighten role-based access controls (RBAC) within SAP S/4HANA Defense & Security to ensure users have the minimum necessary privileges, especially for remote-enabled function modules. 2. Monitor SAP system logs and database change records for unusual or unauthorized direct updates to standard tables, implementing alerting mechanisms for suspicious activity. 3. Apply SAP vendor patches or security notes addressing CVE-2026-24326 as soon as they become available; maintain close communication with SAP support channels for updates. 4. Conduct regular audits of user privileges and remote function call usage to detect potential misuse or privilege escalation attempts. 5. Implement network segmentation and restrict access to SAP systems to trusted hosts and users, reducing exposure to network-based attacks. 6. Employ multi-factor authentication (MFA) for SAP user accounts to reduce the risk of credential compromise. 7. Educate SAP administrators and security teams about this vulnerability and the importance of authorization checks in SAP modules. 8. Consider deploying SAP-specific security tools that can detect anomalous function module invocations or unauthorized database modifications. These targeted measures go beyond generic patching and help reduce the risk of exploitation in complex SAP environments.

Description

CVE-2026-24326 is a medium-severity vulnerability in SAP S/4HANA Defense & Security (Disconnected Operations) caused by a missing authorization check. An attacker with valid user privileges can invoke remote-enabled function modules to directly update standard SAP database tables without proper authorization. This flaw impacts data integrity but does not affect confidentiality or availability. The vulnerability affects multiple versions of SAP S/4HANA Defense & Security, from EA-DFPS 600 through 809. Exploitation requires network access and valid user credentials but no user interaction. No known exploits are currently reported in the wild. European organizations using affected SAP modules, especially in defense and security sectors, should prioritize patching and access control reviews. Countries with significant SAP deployments and strategic defense industries, such as Germany and France, are most likely impacted. Mitigation involves implementing strict role-based access controls, monitoring for unusual database modifications, and applying vendor patches once available. Overall, the vulnerability poses a moderate risk due to its limited impact scope and exploitation prerequisites.

Impact

For European organizations, especially those in defense, government, and critical infrastructure sectors relying on SAP S/4HANA Defense & Security, this vulnerability poses a risk to data integrity. Unauthorized modifications to SAP database tables could lead to incorrect or manipulated security configurations, audit logs, or operational data, potentially undermining security postures or compliance with regulatory requirements such as GDPR or NIS Directive. Although confidentiality and availability are not impacted, integrity breaches in defense-related systems can have serious operational consequences. The requirement for user privileges limits the attack surface to insiders or compromised accounts, but given the sensitivity of defense data, even low-integrity impacts can have outsized effects. European organizations with extensive SAP deployments must consider the risk of insider threats or lateral movement by attackers who have gained user-level access. The lack of known exploits reduces immediate urgency but does not eliminate the risk of future exploitation. The broad range of affected versions means many organizations may be vulnerable if not updated. The impact is thus moderate but significant in high-security environments.

Summary

CVE-2026-24326 identifies a missing authorization check vulnerability (CWE-862) in the Disconnected Operations component of SAP S/4HANA Defense & Security. This flaw allows an attacker who already has user-level privileges within the SAP environment to call remote-enabled function modules that perform direct updates on standard SAP database tables without undergoing proper authorization validation. The vulnerability affects a wide range of SAP S/4HANA Defense & Security versions, from EA-DFPS 600 through 809, indicating a long-standing issue across multiple releases. The core technical issue is that the system fails to enforce authorization checks before allowing remote function calls to modify critical database records, which can lead to unauthorized data manipulation. The CVSS v3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based (AV:N), requires low attack complexity (AC:L), needs privileges (PR:L), and does not require user interaction (UI:N). The impact is limited to integrity (I:L) with no confidentiality (C:N) or availability (A:N) impact. No public exploits have been reported yet, but the vulnerability could be leveraged by insiders or attackers who have compromised user credentials. The missing authorization check could allow unauthorized changes to defense and security-related data, potentially affecting operational decisions or compliance. The vulnerability is particularly relevant for organizations using SAP S/4HANA Defense & Security modules in disconnected or remote operational contexts, where function modules are exposed for remote invocation.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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:42 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats