dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-0491

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical vulnerability in SAP Landscape Transformation allows an attacker with admin privileges to inject arbitrary ABAP code or OS commands through a function module exposed via RFC. The flaw bypasses essential authorization checks and effectively creates a backdoor, enabling full system compromise.

MitigationRestrict or disable RFC exposure of vulnerable function modules, apply SAP security notes/patches, and implement proper authorization validation for admin-level operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Landscape Transformation installation
    Query SAP system for installed SAP LT components. Use transaction code SAPLSA or check via SAINT (SAP Add-On Installation Tool) for the presence of SAP Landscape Transformation add-on. Alternatively, check system tables like CVERS or view installed software components via transaction SM37 or SE16N searching table CVERS.
    Affected if SAP Landscape Transformation is installed and running in the environment
  2. Check RFC exposure of function modules
    Use transaction code SM59 to review RFC destinations and verify if function modules related to SAP LT are exposed via RFC. Check RFC authority checks (transaction code SECSTORE or review authority objects S_RFC and S_RFCACL). Inspect if unrestricted RFC access is granted to function modules in the SAP LT namespace (typically SAPLW*).
    Affected if Function modules in the SAP LT namespace are exposed via RFC without proper authorization controls
  3. Review admin privilege assignments
    Examine user master records (transaction SU01) and role assignments (transaction PFCG) for users with administrative privileges in SAP LT. Check for composite roles containing SAP_LANDSCAPE_TRANSFORMATION_ADMIN or similar. Use transaction SUIM to search for users assigned to roles with broad SAP LT authorizations.
    Affected if Users with admin-level privileges exist and are assigned to SAP LT administrative roles
  4. Inspect for custom or suspicious function modules
    Use transaction code SE37 to browse function modules within the SAP LT function groups. Look for function modules with names indicating code execution capability (e.g., *EXEC*, *COMMAND*, *SHELL*). Review function module attributes for the parameter type and any custom ABAP code that might allow arbitrary command injection.
    Affected if Custom or modified function modules exist in the SAP LT namespace that allow arbitrary ABAP or OS command execution
  5. Review RFC audit logs for suspicious activity
    Check transaction code STAD (Statistical Record) and monitor RFC logs via SM37 for unusual function module calls to SAP LT components. Look for execution patterns outside normal business hours or from unexpected source systems. Review authorization failure logs in transaction code SUIM under the Authorization Failed node.
    Affected if RFC calls to SAP LT function modules originate from unexpected sources or show unusual execution patterns

A system is affected if SAP Landscape Transformation is installed with function modules exposed via RFC and admin privileges are assigned, allowing an attacker to bypass authorization checks and inject arbitrary ABAP or OS commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable RFC exposure of vulnerable function modules, apply SAP security notes/patches, and implement proper authorization validation for admin-level operations.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,784.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0491 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data