# CVE-2026-0504: Insufficient Input Handling in JNDI Operations of SAP Identity Management

> Authenticated administrators can exploit insufficient input handling in JNDI operations to disclose or modify data in SAP Identity Management.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-jm7g-m582-79q7

## What is CVE-2026-0504?

CVE-2026-0504 is a low-severity code injection vulnerability in SAP_SE SAP Identity Management, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to insufficient input handling, the SAP Identity Management REST interface allows an authenticated administrator to submit specially crafted malicious REST requests that are processed by JNDI operations without adequate input neutralization. This may lead to limited disclosure or modification of data, resulting in low impact on confidentiality and integrity, with no impact on application availability.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-0504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0504 is a low-severity code injection vulnerability in SAP_SE SAP Identity Management, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0504 in the wild and no public exploit code.

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

## Sources

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

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