Missing AuthorizationWeakness · CWE-862

CVE-2026-44754

MEDIUM · 6.6 CVSS v3.1 Published 2026-06-09

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

72/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

The Remote Function Call (RFC) modules of the Operational Data Provisioning Data Replication API (ODP-RFC) are missing caller identification of permitted SAP-internal applications and are being used by customer or third-party applications in ways that are not aligned with its intended usage. Which could lead to unintended disclosure of data, but does not affect integrity, and poses minimal availability concerns for the application.

Technical summary

dbcve analysis · moderate confidence

The ODP-RFC API's RFC modules lack proper caller identification mechanisms to verify that only permitted SAP-internal applications are invoking them. Customer or third-party applications can call these modules in ways not intended by SAP design, leading to unintended data disclosure. This is a confidentiality-only issue with no integrity or availability impact.

MitigationImplement caller identification and authorization checks in the ODP-RFC RFC modules to ensure only permitted SAP-internal applications can access sensitive data, blocking unauthorized customer or third-party application calls.

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

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify ODP-RFC module deployment

In the SAP system, use transaction SE11 or SE16 to search for ODP-RFC related objects (tables like TFDIR, TRFCST, or look for function modules with 'ODP' or 'ODP_RFC' in the name). Check if the ODP-RFC modules are installed in your system.

Affected if ODP-RFC modules are found installed in the system without additional caller authorization controls configured.
Review RFC authorization configuration

Use transaction SM30 to view table RFCDES (RFC destinations) and check if ODP-RFC destinations are defined. Use transaction SRTUTIL or SRT_MNG to review ODP (Operational Data Provisioning) related RFC settings.

Affected if ODP-RFC destinations exist but no explicit caller verification (such as ICF service authorization or RFC authorization checks) is configured.
Check caller allowlist or ACL configuration

Examine SAP system authorization roles (transaction PFCG) and profile parameters (transaction RZ11) for parameters related to RFC caller validation. Look for authorization objects S_RFC, S_RFCACL, or custom authorization objects that control ODP-RFC module access.

Affected if No allowlist exists restricting ODP-RFC module access to SAP-internal applications only, or no ACL-based caller verification is active.
Verify ICF handler configuration

Use transaction SICF (Internet Communication Framework) to check if ODP-related services are exposed and whether they have proper authentication/authorization handlers configured for caller validation.

Affected if ODP services in ICF are active without restrictive caller authentication mechanisms enabled.

If ODP-RFC modules are present and no explicit caller identification or authorization controls are configured to restrict access to SAP-internal applications only, the environment is affected by this vulnerability.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement caller identification and authorization checks in the ODP-RFC RFC modules to ensure only permitted SAP-internal applications can access sensitive data, blocking unauthorized customer or third-party application calls.

Have this fixed Scoped from the published advisory

Consultation8.0 h
Implementation24.0 h
Testing16.0 h
Review / QA8.0 h

56.0 hours of engineering $9,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-44754 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-44754?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.6 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 56 hrs · Moderate

Typical engagement from $9,760

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-44754 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References