CVE-2026-24319VulnerabilityPublished 10 Feb 2026Updated 26 Feb 2026

CVE-2026-24319: SAP Business One (B1 Client Memory Dump Files) · Cleartext Storage of Sensitive Information in Memory

Affects SAP Business One (B1 Client Memory Dump Files)Source CVE Database V5

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.8Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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-26.

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 Business One (B1 Client Memory Dump Files)	Affected =B1_ON_HANA 10.0 =SAP-M-BO 10.0	Fixed in–

AI-suggested

To mitigate CVE-2026-24319, organizations should implement strict access controls on systems running SAP Business One to ensure only authorized personnel have local access, especially with elevated privileges. Limit the generation and retention of memory dump files to the minimum necessary for troubleshooting, and securely delete or encrypt these files to prevent unauthorized reading. Monitor and audit access to memory dump files and related directories to detect suspicious activity. Apply the principle of least privilege to reduce the number of users with high-level access. Coordinate with SAP for official patches or updates addressing this vulnerability and deploy them promptly once available. Additionally, consider implementing endpoint detection and response (EDR) solutions to detect anomalous access patterns or attempts to extract sensitive data from memory. Educate administrators and users about the risks of exposing sensitive information through memory dumps and enforce policies to handle such files securely.

Description

In SAP Business One, sensitive information is written to the application�s memory dump files without obfuscation. Gaining access to this information could potentially lead to unauthorized operations within the B1 environment, including modification of company data. This issue results in a high impact on confidentiality and integrity, with no impact on availability.

Impact

The primary impact of this vulnerability is on the confidentiality and integrity of sensitive business data within SAP Business One environments. If exploited, attackers with local privileged access can extract sensitive information from memory dump files, potentially including credentials or session tokens, which can be leveraged to perform unauthorized operations such as data modification or unauthorized access to business-critical functions. This can lead to financial loss, regulatory compliance violations, and damage to organizational reputation. Since the vulnerability does not affect availability, denial-of-service scenarios are unlikely. However, the requirement for high privileges and user interaction limits the attack surface to insider threats or attackers who have already compromised a system with elevated rights. Organizations with SAP Business One deployments, especially in sectors handling sensitive financial or operational data, face increased risk if local access controls are weak or if memory dump files are not properly secured.

CWE-316Cleartext Storage of Sensitive Information in Memory (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in memory.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (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 27 Feb 2026, 08:08 UTC

WeaknessesCWE-316

Technical details

References

Community reviews

Related threats