LiveActive security incident?Get immediate response
CVE Record

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

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.

LowCVSS 3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-0510 is a low-severity SAP NetWeaver AS Java issue where UME User Mapping encrypts data with an obsolete algorithm. An attacker already holding high privileges may, under specific conditions, partially disclose sensitive information. The published scoring indicates no integrity or availability impact.

Executive priority

Handle through normal SAP patch governance, not emergency response, unless affected systems store especially sensitive mappings or have weak privileged-access controls. The business risk is limited confidentiality exposure, but it still warrants validation because the affected software supports identity and user mapping functions.

Technical view

SAP NW AS Java UME User Mapping uses weak/obsolete cryptography for User Mapping data, mapped to CWE-326. Affected components listed are ENGINEAPI 7.50, SERVERCORE 7.50, and UMEADMIN 7.50. CVSS 3.1 is 3.0: network vector, high attack complexity, high privileges required, scope changed, low confidentiality impact only.

Likely exposure

Exposure appears limited to SAP NetWeaver AS Java environments using the listed UME User Mapping components at version 7.50. The source bundle states default status is unaffected outside the named affected components, but organizations should confirm against SAP Note 3593356.

Exploitation context

No active exploitation is indicated in the provided sources, and this CVE is not marked KEV. Exploitation requires high-privileged access and specific conditions, reducing likelihood. The main risk is partial disclosure of sensitive User Mapping information, not system takeover or service disruption.

Researcher notes

The public record does not describe the obsolete algorithm, exact data format, prerequisites beyond high privileges, or a named patch level. Avoid assuming exploitability beyond the CVSS and SAP description. Use SAP Note 3593356 as the authoritative source for affected build and remediation details.

Mitigation direction

  • Review SAP Note 3593356 for official remediation guidance.
  • Check SAP Security Patch Day material for related updates.
  • Prioritize affected SAP NW AS Java 7.50 components in patch planning.
  • Limit and monitor high-privileged access to UME administration functions.
  • Treat User Mapping data as sensitive during response review.

Validation and detection

  • Inventory SAP NW AS Java deployments and installed component versions.
  • Confirm whether ENGINEAPI, SERVERCORE, or UMEADMIN 7.50 are present.
  • Compare system status with SAP Note 3593356 guidance.
  • Review privileged UME access assignments for unnecessary rights.
  • Monitor vendor updates for revised severity or remediation details.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-326: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0510 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N1.31.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3Low
CVSS 3.1 vector shape for CVE-2026-0510Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAP_SENW AS Java UME User MappingENGINEAPI 7.50, SERVERCORE 7.50, UMEADMIN 7.50unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.