CVE-2026-0509
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 · uneditedSAP NetWeaver Application Server ABAP and ABAP Platform allows an authenticated, low-privileged user to perform background Remote Function Calls without the required S_RFC authorization in certain cases. This can result in a high impact on integrity and availability, and no impact on the confidentiality of the application.
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 confidenceThis vulnerability in SAP NetWeaver Application Server ABAP and ABAP Platform allows authenticated, low-privileged users to execute background Remote Function Calls (RFC) without the required S_RFC authorization, bypassing standard access controls in certain scenarios.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.22= 7.53= 7.54= 7.77= 7.89= 7.93= 9.16= 9.18= 9.19= 7.22= 7.22ext= 7.22= 7.22ext= 7.53CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SAP NetWeaver ABAP kernel versionExecute transaction SM51 or use the SAP kernel version check command: 'SAPCAR -tvf <kernel_archive>' or check the kernel directory files (disp+work executable)Affected if The installed kernel version matches one of the affected versions: 7.22, 7.53, 7.54, 7.77, 7.89, 7.93, 9.16, 9.18, or 9.19 (for Kernel); 7.22 or 7.22ext (for Krnl64nuc); 7.22, 7.22ext, or 7.53 (for Krnl64uc)
-
Verify background RFC is enabledCheck SAP transaction code SM37 (background job monitoring) or SM49 (RFC authorities) to confirm RFC functionality is active in the systemAffected if Background RFC execution capability is present and active in the SAP environment
-
Review S_RFC authorization assignmentsUse transaction code SUIM (User Information System) to query authorization objects S_RFC and examine which users or roles have this authorization granted, focusing on low-privileged accountsAffected if Users lacking proper S_RFC authorization are able to schedule or execute background RFC jobs, indicating the bypass condition exists
-
Inspect RFC function module execution logsCheck transaction code SLG1 (Application Log) or SM37 for RFC-related job logs and look for executions initiated by users without documented S_RFC rightsAffected if Background RFC jobs are logged as executed by users who do not hold the S_RFC authorization object
A system is affected if it runs an affected SAP NetWeaver ABAP kernel version AND has background RFC functionality enabled AND allows low-privileged authenticated users to execute RFC jobs without proper S_RFC authorization.
Generated from the published advisory. Verify against your own configuration.
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 dataApply relevant SAP security notes/patches to address the authorization bypass. Review and adjust S_RFC authorizations in affected roles to enforce proper access controls for background RFC operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0509 in production — separate from our analysis above.
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.
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.
- 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