CVE-2026-0484VulnerabilityPublished 10 Feb 2026

CVE-2026-0484: SAP NetWeaver Application Server ABAP and SAP S/4HANA · URL Redirection to Untrusted Site

Affects SAP NetWeaver Application Server ABAP and SAP S/4HANASource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: 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 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 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 NetWeaver Application Server ABAP and SAP S/4HANA	Affected =SAP_BASIS 700 =SAP_BASIS 701 =SAP_BASIS 702 =SAP_BASIS 731 =SAP_BASIS 740 =SAP_BASIS 750 =SAP_BASIS 751 =SAP_BASIS 752 =SAP_BASIS 753 =SAP_BASIS 754 =SAP_BASIS 755 =SAP_BASIS 756 =SAP_BASIS 757 =SAP_BASIS 758 =SAP_BASIS 816	Fixed in–

AI-suggested

1. Apply SAP security patches promptly once they are released for the affected SAP_BASIS versions to address the missing authorization check. 2. Conduct a thorough review and tighten access controls on transaction codes related to text data modification, ensuring only authorized personnel have access. 3. Implement robust authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Monitor and audit SAP system logs for unusual access patterns or unauthorized transaction code usage, focusing on changes to text data. 5. Use SAP’s security notes and tools to identify and remediate configuration weaknesses that could facilitate exploitation. 6. Educate SAP administrators and users about the risks of this vulnerability and the importance of adhering to least privilege principles. 7. Segment SAP environments and restrict network access to minimize exposure of SAP systems to untrusted networks. 8. Employ anomaly detection systems to identify potential integrity violations or suspicious modifications in SAP data. These steps go beyond generic advice by focusing on transaction code access control, monitoring, and SAP-specific security practices.

Description

CVE-2026-0484 is a medium-severity vulnerability in SAP NetWeaver Application Server ABAP and SAP S/4HANA that allows an authenticated attacker with limited privileges to exploit a missing authorization check. This flaw enables modification of text data within the system, impacting data integrity without affecting confidentiality or availability. The vulnerability arises from improper validation related to URL redirection (CWE-601) and affects multiple SAP_BASIS versions from 700 through 816. Exploitation requires authentication but no user interaction, and no known exploits are currently reported in the wild. The vulnerability's impact is primarily on the integrity of application data, which could lead to unauthorized changes in business-critical information. European organizations using affected SAP versions are at risk, especially those with extensive SAP deployments in finance, manufacturing, and supply chain sectors. Mitigation requires applying SAP patches once available and implementing strict access controls and monitoring of transaction codes. Countries with significant SAP market penetration and critical infrastructure relying on SAP, such as Germany, France, and the UK, are most likely to be affected. The CVSS score of 6.5 reflects a medium severity due to the integrity impact and the need for authenticated access.

Impact

The primary impact of CVE-2026-0484 is on the integrity of SAP application data, allowing an authenticated attacker to modify text data within the system. For European organizations, this could lead to unauthorized changes in critical business information such as financial records, supply chain data, or operational parameters, potentially causing incorrect reporting, compliance violations, or operational disruptions. Since SAP systems are widely used across Europe in sectors like manufacturing, finance, energy, and public administration, the integrity compromise could have cascading effects on business decisions and regulatory adherence. Although confidentiality and availability are not directly affected, the trustworthiness of data is critical in enterprise environments, and manipulation could facilitate fraud, sabotage, or data corruption. The requirement for authenticated access limits the risk to insiders or attackers who have already compromised user credentials, emphasizing the importance of strong identity and access management. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time. Organizations relying heavily on SAP S/4HANA and NetWeaver platforms should consider this vulnerability a significant risk to data integrity and operational reliability.

Summary

CVE-2026-0484 is a vulnerability identified in SAP NetWeaver Application Server ABAP and SAP S/4HANA platforms, specifically affecting multiple SAP_BASIS component versions ranging from 700 to 816. The root cause is a missing authorization check that allows an authenticated attacker with limited privileges to access a particular transaction code and modify text data within the system. This vulnerability is categorized under CWE-601 (URL Redirection to Untrusted Site), indicating that the flaw involves improper handling of URL redirection mechanisms, potentially enabling attackers to redirect users or processes to untrusted sites or manipulate internal data flows. However, in this case, the primary impact is on the integrity of the application data rather than confidentiality or availability. The attacker does not require user interaction but must have some level of authenticated access (PR:L in CVSS), which lowers the barrier compared to requiring administrative privileges but still restricts exploitation to insiders or compromised accounts. The vulnerability does not affect confidentiality or availability, meaning sensitive data leakage or denial of service is not a concern here, but unauthorized modification of text data could disrupt business processes, reporting, or compliance. No known exploits have been reported in the wild as of the publication date, but the broad range of affected SAP_BASIS versions and the critical role of SAP systems in enterprise environments make this a significant concern. The CVSS v3.1 score of 6.5 reflects a medium severity, balancing the ease of exploitation with the impact scope. SAP customers should monitor for official patches and advisories and review access controls around the affected transaction codes.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (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:32 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats