# CVE-2026-44749: Information Disclosure vulnerability in SAP Gateway

> Attackers can inject content into error messages to disclose request artifacts and URI parsing logic, impacting confidentiality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-53r4-mvj6-w855

## What is CVE-2026-44749?

CVE-2026-44749 is a medium-severity vulnerability in SAP_SE SAP Gateway, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SAP Gateway allows attackers to inject content into error messages, potentially leading to disclosure of request artefacts (e.g., regex patterns) and revealing underlying URI parsing logic. Leading to low impact on confidentiality. Integrity and availability are unaffected.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-44749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44749 is a medium-severity vulnerability in SAP_SE SAP Gateway, published on 26 May 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-44749 in the wild and no public exploit code.

Affected product: SAP_SE SAP Gateway. 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-44749/ (Markdown: https://insights.sbomify.com/CVE-2026-44749/index.md)
```

## Sources

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

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