CVE-2026-109811SAP_SE SAP NetWeaver and ABAP Platform (Application Server ABAP) server-side request forgery
CVE-2026-109811 is a server-side request forgery in SAP_SE SAP NetWeaver and ABAP Platform (Application Server ABAP), rated medium (6.5 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place SAP_SE SAP NetWeaver and ABAP Platform (Application Server ABAP) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
An internal ABAP HTTP component in SAP NetWeaver and ABAP Platform (Application Server ABAP) has SSRF vulnerability due to insecure default settings. An authenticated attacker with low privileges could trick the victim to interact with a malicious server which allows the attacker to access sensitive information belonging to the victim and modify limited non-sensitive information. This results in a high impact on confidentiality and low impact on integrity. Availability is not impacted.
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
- Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.
Questions to answer about your own systems
- Where does SAP_SE SAP NetWeaver and ABAP Platform (Application Server ABAP) 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.