# CVE-2026-44744: SQL Injection vulnerability in SAP S/4HANA

> An authenticated attacker can execute unauthorized database queries in SAP S/4HANA to access sensitive information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-wxg7-5pqj-jxrf

## What is CVE-2026-44744?

CVE-2026-44744 is a medium-severity SQL injection vulnerability in SAP_SE SAP S/4HANA, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S/4HANA(On-Premise) contains SQL injection vulnerability in a remote-enabled function module component that could be exploited by an authenticated attacker to potentially execute unauthorized database queries.This flaw exposes sensitive information to which they should not otherwise have access to. The vulnerability has a high impact on the confidentiality of the data with no impact on the integrity and availability of the application.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-44744?


## How do I fix CVE-2026-44744?

No fix has been published for CVE-2026-44744 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44744 being exploited?

There is no known exploitation of CVE-2026-44744 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44744 and fix it if it is affected.

What it is: CVE-2026-44744 is a medium-severity SQL injection vulnerability in SAP_SE SAP S/4HANA, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44744 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44744/ (Markdown: https://insights.sbomify.com/CVE-2026-44744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44744
- OSV: https://osv.dev/vulnerability/CVE-2026-44744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44744/
Summaries are generated and may contain mistakes; the official description above is the record.