LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0491: Code Injection vulnerability in SAP Landscape Transformation

SAP Landscape Transformation allows an attacker with admin privileges to exploit a vulnerability in the function module exposed via RFC. This flaw enables the injection of arbitrary ABAP code/OS commands into the system, bypassing essential authorization checks. This vulnerability effectively functions as a backdoor, creating the risk of full system compromise, undermining the confidentiality, integrity and availability of the system.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-0491 is a critical SAP Landscape Transformation flaw. An attacker who already has admin privileges could abuse an RFC-exposed function module to inject ABAP code or OS commands, bypass authorization checks, and potentially take full control of the SAP system.

Executive priority

Treat as urgent for SAP environments using Landscape Transformation. Although admin privileges are required, compromise of such an account could lead to full system compromise affecting business-critical data, operations, and trust in SAP-controlled processes.

Technical view

The vulnerability is CWE-94 code injection in SAP Landscape Transformation DMIS versions 2011_1_700, 2011_1_710, 2011_1_730, 2011_1_731, 2018_1_752, and 2020. CVSS 3.1 is 9.1: network reachable, low complexity, high privileges required, no user interaction, scope changed, high CIA impact.

Likely exposure

Exposure is likely limited to organizations running affected SAP Landscape Transformation DMIS versions with RFC access paths reachable by privileged users or compromised admin accounts. The source states default status is unaffected outside listed versions.

Exploitation context

The CVE record does not report active exploitation, and this CVE is not marked KEV in the provided data. Exploitation requires high privileges, but impact is severe because the flaw can bypass authorization checks and function like a backdoor.

Researcher notes

Evidence comes from the CVE record and SAP references. Public details are limited; no exploit status or specific patch contents are provided in the bundle. Avoid assuming exposure beyond the listed DMIS versions and confirm remediation through SAP Note 3697979.

Mitigation direction

  • Review SAP Note 3697979 and SAP Security Patch Day guidance.
  • Apply SAP-provided corrections for affected DMIS versions if available.
  • Restrict RFC access to trusted administrative users only.
  • Audit SAP admin accounts for compromise or excessive privilege.
  • Monitor SAP systems for unauthorized ABAP or OS command activity.

Validation and detection

  • Inventory SAP Landscape Transformation and DMIS component versions.
  • Confirm whether any listed affected DMIS version is installed.
  • Review RFC-exposed function modules and administrative access paths.
  • Check whether SAP Note 3697979 corrections are applied.
  • Review logs for suspicious privileged RFC activity.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0491 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-0491Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAP_SESAP Landscape TransformationDMIS 2011_1_700, 2011_1_710, 2011_1_730, 2011_1_731, 2018_1_752, 2020unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.