Pathlock logo
Schedule Demo
Pathlock

SAP Note 3834842: How to Check for Signs of Compromise

3-min read
Published: 11.20.2026
|
Updated: 11.20.2026

SAP Note 3834842:

How to Check for Signs of Compromise

Download Full Advisory

On 10 November 2026, SAP released HotNews note 3834842, addressing a vulnerability rated 9.9 on the CVSS scale.

Applying SAP’s fix does not tell security teams whether a system was compromised before patching. The affected functions do not log submitted content or the actions it triggers. A successful remote call alone does not prove exploitation, and missing logs cannot rule it out.

Pathlock’s research addresses this detection challenge. The team reproduced the authorization weakness and checked logging behavior using harmless laboratory tests. The advisory explains what evidence defenders can collect, how to connect suspicious calls to other activity, and which findings warrant an incident investigation.

What was found

The flaw, tracked as CVE-2026-109795, affects certain SAP S/4HANA CRM and SAP CRM components. Two remote-enabled functions, CATX_XSLT_TRANSFORM and CATX_XSLT_TRANSFORM2, process XML and stylesheet content supplied by the caller. Before SAP’s fix, they did not apply sufficient authorization or validation to that content. An authenticated attacker with low privileges and access to the remote interface could cause the system to process attacker-controlled content, which SAP says can lead to arbitrary code execution.

Affected versions are S4CRM 204–206, S4CEXT 107–109 and BBPCRM 713–714. SAP states that there is no workaround, so installing the complete fix is the only way to close the gap.

Critical: Key facts
  • CVE: CVE-2026-109795
  • CVSS: 9.9 (Critical)
  • SAP Note: 3834842
  • Attacker needs: a valid user able to call the affected functions, plus network access
  • Workaround: none
  • Action: apply SAP’s complete fix as soon as possible

Why detection is hard

The affected functions do not log submitted content or the actions it triggers, making exploitation difficult to detect. A successful remote-call entry in the Security Audit Log shows only that a call was accepted—not that exploitation occurred. Legitimate CRM tools may use the same functions. The functions do not write a dedicated rejection log; other records may still show the invocation. Relevant audit events may also be disabled, and statistical records may have expired.

Missing logs do not prove that a system is clean.

Five steps to check for compromise

  1. Confirm exposure.

    Identify affected systems and verify that SAP’s complete fix is installed, including every stage of a staged correction. Investigate unpatched and partially patched systems first.

  2. Preserve and check logging.

    Collect Security Audit Log and statistical (STAD) records before they expire, and make sure remote function calls and report starts are captured. Enabling logging now will not recover past activity.

  3. Look for unexpected callers.

    Search available history for calls to the two functions, and investigate any account or calling system that does not normally use them.

  4. Connect suspicious calls to other activity.

    Correlate the same account and time frame across execution records and authorization traces. Look for follow-on changes to users, permissions, code, remote connections or scheduled jobs, and for unusual outbound traffic.

  5. Escalate suspicious combinations.

    An unexpected call on an unpatched system, backed by execution evidence or suspicious follow-on changes, warrants an incident investigation. Restrict the suspected account and preserve evidence.

One caution applies throughout: a successful call alone does not confirm compromise. Confirmation requires recovered malicious content or forensic evidence of what the attacker did.

What to do now

Apply SAP’s complete fix as soon as possible. While approvals are pending, reduce exposure by removing remote-call authorization for these functions from every role that does not need it, restricting network access to the RFC gateway, and turning on the monitoring described above. These measures lower risk but do not replace the fix.

Pathlock’s full advisory covers the affected versions and fixed support packages, the evidence sources and recommended retention periods, the detection signals and how to combine them, and compensating controls. Download it here.

See Pathlock in action

Your privacy is important to us. Privacy Policy