# CVE-2026-44753: Information Disclosure vulnerability in SAP HANA Extended Application Services classic model (User Self Service)

> Unauthenticated attackers can enumerate valid user accounts and email addresses in SAP HANA XSA User Self Service via crafted requests.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-q32w-qvcr-5jr4

## What is CVE-2026-44753?

CVE-2026-44753 is a low-severity vulnerability in SAP_SE SAP HANA Extended Application Services classic model (User Self Service), published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP HANA Database (user self service tools) allows an unauthenticated user to send specially crafted requests that produce distinguishable responses, enabling enumeration of valid user accounts and email addresses. Successful exploitation could allow the attacker to enumerate valid user accounts, resulting in low impact on confidentiality, with no impact on integrity and availability of the application.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2026-44753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44753 is a low-severity vulnerability in SAP_SE SAP HANA Extended Application Services classic model (User Self Service), published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44753 in the wild and no public exploit code.

Affected product: SAP_SE SAP HANA Extended Application Services classic model (User Self Service). 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-44753/ (Markdown: https://insights.sbomify.com/CVE-2026-44753/index.md)
```

## Sources

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

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