CVE-2026-58240: Missing Authentication check in SAP NetWeaver (Message Server)
SAP NetWeaver Message Server does not sufficiently validate the authenticity of internal application server components during registration. An unauthenticated attacker with network access to the affected service could exploit this weakness to register an unauthorized component and potentially perform unauthorized actions within the application environment, resulting in a high impact on the confidentiality, integrity, and availability of the affected system.
Security readout for executives and security teams
Plain-English summary
A network attacker could impersonate an internal SAP application server component and register it with the NetWeaver Message Server without authentication. Successful abuse could expose data, alter application activity, or disrupt affected SAP environments. No user interaction or existing account is required, making reachable systems especially urgent to assess.
Executive priority
Prioritize immediate identification of affected Message Servers, beginning with externally or broadly reachable systems. Restrict access while teams obtain and test SAP’s prescribed remediation. Because compromise could affect sensitive business data, transactions, and service availability without credentials, track remediation as a critical operational risk.
Technical view
CVE-2026-58240 is a CWE-308 missing-authentication flaw in SAP NetWeaver Message Server component registration. The listed affected releases are KERNEL 9.16, 9.18, 9.19, and 9.20. It carries CVSS 3.1 score 9.8 because exploitation is network-based, low-complexity, unauthenticated, and may severely affect confidentiality, integrity, and availability.
Likely exposure
Exposure requires network access to an affected Message Server service. Risk is greatest where the service is reachable from untrusted, user, partner, or insufficiently segmented networks. The supplied record identifies only KERNEL 9.16, 9.18, 9.19, and 9.20 as affected; confirm actual deployed versions rather than assuming all NetWeaver installations are vulnerable.
Exploitation context
The bundle reports that this CVE is not in KEV and provides no evidence of active exploitation. It nevertheless describes a remotely reachable, unauthenticated, low-complexity weakness with potentially complete system impact. Treat exposed affected services as urgent without representing exploitation as confirmed.
Researcher notes
The public bundle establishes the authentication failure, affected kernel releases, and impact rating, but does not provide protocol details, indicators of compromise, patch identifiers, or confirmed exploitation. Avoid inferring additional affected releases. Defensive assessment should focus on version confirmation, service reachability, registration trust boundaries, and anomalies in registered components.
Mitigation direction
Review SAP Note 3759472 and SAP Security Patch Day guidance for the vendor-approved remediation.
Apply the vendor-prescribed update or configuration change after appropriate testing.
Restrict Message Server access to explicitly authorized application components and trusted network segments.
Block unnecessary exposure through firewalls, access controls, and network segmentation.
Increase monitoring for unexpected component registrations or unauthorized application activity.
Validation and detection
Inventory NetWeaver Message Server deployments and record their exact SAP KERNEL versions.
Confirm whether each Message Server is reachable from untrusted or broadly accessible network segments.
Compare registered application server components against an approved asset inventory.
Review available SAP logs and monitoring for unexpected registrations or unexplained configuration changes.
Verify the vendor-prescribed remediation is installed and effective using SAP-supported checks.
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-308: 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.
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
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-308 · source CWE mapping
Use of Single-factor Authentication
Use of Single-factor Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.