CVE-2026-0486VulnerabilityPublished 10 Feb 2026

CVE-2026-0486: ABAP based SAP systems · Missing Authorization

Affects ABAP based SAP systemsSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.0Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% 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:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
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: 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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 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_SEABAP based SAP systems	Affected =2008_1_710 =740 =758	Fixed in–

AI-suggested

1. Conduct a thorough review of user access rights within SAP systems to ensure that only authorized personnel have access to sensitive function modules. 2. Implement strict authentication and session management policies to reduce the risk of credential compromise. 3. Monitor SAP system logs and network traffic for unusual access patterns or attempts to invoke remote-enabled function modules unexpectedly. 4. Apply SAP security notes and patches promptly once they become available for the affected versions. 5. Use SAP's built-in authorization concepts to enforce the principle of least privilege, restricting access to function modules based on job roles. 6. Consider deploying network segmentation and firewall rules to limit access to SAP systems from untrusted networks. 7. Educate SAP administrators and users about the risks associated with this vulnerability and the importance of secure credential management. 8. If patching is delayed, implement compensating controls such as enhanced monitoring and temporary access restrictions to mitigate risk.

Description

CVE-2026-0486 is a medium severity vulnerability affecting ABAP based SAP systems where a remote-enabled function module fails to perform necessary authorization checks for authenticated users. This results in unauthorized disclosure of system information, impacting confidentiality with no effect on integrity or availability. The vulnerability affects specific versions including ST-PI 2005_1_700, 2008_1_710, 740, and 758. Exploitation requires network access and authenticated user privileges but no user interaction. Although no known exploits are currently reported in the wild, the vulnerability poses a risk of information leakage that could aid further attacks. European organizations using these SAP versions should prioritize patching or mitigating this issue to prevent unauthorized data exposure. Countries with significant SAP deployments, such as Germany and the UK, are particularly at risk. Mitigation involves strict access control reviews, monitoring for unusual access patterns, and applying SAP security notes once available. Given the medium CVSS score of 5.0, the threat is moderate but should not be overlooked due to the critical role SAP systems play in enterprise operations.

Impact

For European organizations, the primary impact of CVE-2026-0486 is the unauthorized disclosure of sensitive system information within SAP environments. This can lead to increased risk of targeted attacks, as attackers may gain insights into system configurations, user roles, or other internal details that facilitate privilege escalation or lateral movement. While the vulnerability does not compromise data integrity or system availability, the leakage of system information can undermine overall security posture and compliance with data protection regulations such as GDPR. Organizations in sectors heavily reliant on SAP, including manufacturing, finance, and logistics, may face operational risks if attackers exploit this vulnerability to gather intelligence. Additionally, the requirement for authenticated access means insider threats or compromised credentials could be leveraged to exploit this flaw. The medium severity rating indicates a moderate risk level, but given SAP's critical role in enterprise resource planning across Europe, the impact could be significant if combined with other vulnerabilities or attack vectors.

Summary

CVE-2026-0486 is a vulnerability classified under CWE-862 (Missing Authorization) that affects ABAP based SAP systems. The issue arises because a remote-enabled function module within these SAP systems does not enforce proper authorization checks for authenticated users. This flaw allows users with valid credentials to access system information that should otherwise be restricted. The vulnerability impacts specific SAP versions, including ST-PI 2005_1_700, 2008_1_710, 740, and 758. The attack vector is network-based, requiring the attacker to have authenticated access but no additional user interaction. The vulnerability leads to unauthorized disclosure of system information, which can be leveraged by attackers for reconnaissance or to facilitate further attacks. However, it does not affect the integrity or availability of the system. The CVSS v3.1 base score is 5.0, reflecting a medium severity level due to the limited confidentiality impact and the requirement for authentication. No public exploits have been reported yet, but the vulnerability's presence in widely used SAP systems makes it a concern for organizations relying on these platforms. SAP has not yet published patches, so organizations must rely on compensating controls until updates are available.

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:47 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats