CVE-2026-120017SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider) improper signature verification
CVE-2026-120017 is a improper signature verification in SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider), rated critical (10.0 on CVSS 3.1).
Why this priority: Critical, and reachable over the network without an account.
Published · Updated · NVD status: Awaiting Analysis
What it is
A cryptographic signature is not checked properly, so forged data is accepted.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet. It can be exploited automatically, at scale.
What to do
- No fixed version is listed yet. Find every place SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
- Signature checks. The flaw sits on the network path between clients and services.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.
Questions to answer about your own systems
- Where does SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider) run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.