PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-27675 SAP_SE CVE debrief

SAP Landscape Transformation contains a vulnerability in an RFC-exposed function module that could allow a high privileged adversary to inject arbitrary ABAP code and operating system commands. Due to this, some information could be modified, but the attacker does not have control over kind or degree. This leads to a low impact on integrity, while confidentiality and availability are not impacted.

Vendor
SAP_SE
Product
SAP Landscape Transformation
CVSS
LOW 2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-14
Original CVE updated
2026-10-26
Advisory published
2026-04-14
Advisory updated
2026-10-26

Who should care

SAP administrators, security teams, and IT personnel responsible for SAP Landscape Transformation deployments should assess exposure and potential impact on integrity. They should review and apply available patches or mitigations, and prioritize remediation based on the low impact on integrity.

Why it matters

Defenders should prioritize verifying exposure and assessing potential impact on integrity due to the vulnerability in SAP Landscape Transformation. SAP administrators should review and apply available patches or mitigations.

  • Verify exposure and assess potential impact on integrity.
  • Prioritize remediation based on the low impact on integrity.
  • Monitor SAP security advisories for updates on this vulnerability.

Technical summary

The vulnerability in SAP Landscape Transformation allows a high privileged adversary to inject arbitrary ABAP code and operating system commands through an RFC-exposed function module. This could lead to modification of some information, with a low impact on integrity, while confidentiality and availability are not impacted. The vulnerability affects SAP Landscape Transformation deployments, and defenders should prioritize verifying exposure and assessing potential impact on integrity. SAP administrators should review and apply available patches or mitigations.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact on integrity. SAP administrators should review and apply available patches or mitigations.

Recommended defensive actions

  • Verify exposure by reviewing SAP Landscape Transformation configurations and applying available patches or mitigations.
  • Assess potential impact on integrity and prioritize remediation accordingly.
  • Monitor SAP security advisories for updates on this vulnerability.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. SAP notes and security patch day information are available for further review. To verify exposure, defenders should review SAP Landscape Transformation configurations and assess potential impact on integrity. The vulnerability allows a high privileged adversary to inject arbitrary ABAP code and operating system commands through an RFC-exposed function module.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-27675 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-27675

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-27675 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-27675

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.