Skip to main content
CVE-2026-0492VulnerabilityPublished Updated

CVE-2026-0492: SAP HANA database · Missing Authentication

Affects SAP HANA databaseSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
SAP_SESAP HANA databaseAffected
  • =HDB 2.00
Fixed in–

AI-suggested

To mitigate CVE-2026-0492, organizations should immediately assess their SAP HANA 2.00 deployments for exposure to this vulnerability. Since no official patches are currently available, implement the following specific measures: 1) Restrict network access to SAP HANA management interfaces using firewalls and network segmentation to limit exposure to trusted administrators only. 2) Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 3) Monitor user activity and audit logs for unusual privilege escalation attempts or unauthorized user switches. 4) Apply the principle of least privilege by reviewing and minimizing user permissions to reduce the impact of compromised accounts. 5) Temporarily disable or restrict the use of functions that allow user context switching if feasible. 6) Stay informed on SAP security advisories and apply official patches or updates as soon as they become available. 7) Conduct penetration testing and vulnerability assessments focused on authentication controls within SAP HANA to identify and remediate similar weaknesses. These targeted actions go beyond generic advice and address the specific nature of the missing authentication flaw.

Description

SAP HANA database is vulnerable to privilege escalation allowing an attacker with valid credentials of any user to switch to another user potentially gaining administrative access. This exploit could result in a total compromise of the system�s confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…