CVE-2026-120017: CVE-2026-120017: SAP NetWeaver AS ABAP and ABAP Platform does not perform sufficient verification of incomi…
Unknown · SAP NetWeaver AS ABAP · NVD published 2026-11-10 · posted 2026-11-10 · last modified 2026-11-10
CVE-2026-120017 at a glance
CVE-2026-120017 is a critical-severity Signature Bypass vulnerability in SAP NetWeaver AS ABAP, with a CVSS 3.1 base score of 10. NVD published it on 2026-11-10 and classifies the weakness as CWE-347. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Defense Impairment, inferred from the CWE and the description. Its CVERadar threat level is 50/100.
What it is
SAP NetWeaver AS ABAP and ABAP Platform does not perform sufficient verification of incoming authentication assertions under certain configurations. An unauthenticated attacker could submit specially crafted data to bypass authentication and impersonate arbitrary users, including privileged accounts. Successful exploitation could cause a full system compromise, with the impact potentially extending to connected components and systems beyond the affected system. This results in a high impact on confidentiality, integrity, and availability of the application.
| Weakness | CWE-347 definition |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (source: CNA (sap.com)) |
| ATT&CK tactics | Defense Impairment |
Defend the Chain
The attack chain for CVE-2026-120017 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1553 Subvert Trust Controls Inferred
Inferred from CWE CWE-347
Patches, mitigations and detection
Fixed versions
NVD does not list a fixed version for this CVE. Use the vendor advisory below.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
No vendor-tagged reference yet; see the full reference list.
MITRE ATT&CK mitigations for this chain
- M1038 Execution Prevention (for T1553) : System settings can prevent applications from running that haven't been downloaded through the Apple Store (or other legitimate repositories) which can help mitigate some of these issues. Also enable application control solutions such as AppLocker and/or Device Guard to block the loading of malicious content.
- M1028 Operating System Configuration (for T1553) : Windows Group Policy can be used to manage root certificates and the <code>Flags</code> value of <code>HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\Root\\ProtectedRoots</code> can be set to 1 to prevent non-administrator users from making further root installations into their own HKCU certificate store.
- M1026 Privileged Account Management (for T1553) : Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
- M1024 Restrict Registry Permissions (for T1553) : Ensure proper permissions are set for Registry hives to prevent users from modifying keys related to SIP and trust provider components. Components may still be able to be hijacked to suitable functions already present on disk if malicious modifications to Registry keys are not prevented.
- M1054 Software Configuration (for T1553) : HTTP Public Key Pinning (HPKP) is one method to mitigate potential [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557) situations where and adversary uses a mis-issued or fraudulent certificate to intercept encrypted communications by enforcing use of an expected certificate.
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.
Not sure which of your web apps face the internet? An attack surface review from LayerLogix maps what is exposed.
Sources
- NVD: CVE-2026-120017
- CVE.org record for CVE-2026-120017
- FIRST EPSS score for CVE-2026-120017 (n/a)
- Reference (me.sap.com) me.sap.com/notes/3849308
- Reference (url.sap) url.sap/sapsecuritypatchday