# CVE-2026-0510: Obsolete Encryption Algorithm Used in NW AS Java UME User Mapping

> An attacker with high privileges can exploit obsolete encryption in SAP NetWeaver Java UME to partially disclose sensitive user mapping data.

- **Severity:** Low 3.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/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-cv7h-78v9-r3jf

## What is CVE-2026-0510?

CVE-2026-0510 is a low-severity vulnerability in SAP_SE NW AS Java UME User Mapping, published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The User Management Engine (UME) in NetWeaver Application Server for Java (NW AS Java) utilizes an obsolete cryptographic algorithm for encrypting User Mapping data. This weakness could allow an attacker with high-privileged access to exploit the vulnerability under specific conditions potentially leading to partial disclosure of sensitive information.This has low impact on confidentiality with no impact on integrity and availability of the application.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2026-0510 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0510 is a low-severity vulnerability in SAP_SE NW AS Java UME User Mapping, 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-0510 in the wild and no public exploit code.

Affected product: SAP_SE NW AS Java UME User Mapping. 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-0510/ (Markdown: https://insights.sbomify.com/CVE-2026-0510/index.md)
```

## Sources

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

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