# CVE-2026-120013: Path Traversal in Agent Memory Module of SAP Cloud SDK for Python


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-28c8-457r-4cf6

## What is CVE-2026-120013?

CVE-2026-120013 is a high-severity vulnerability in SAP_SE SAP Cloud SDK for Python, published on 10 Nov 2026. 

### Official description

The agent_memory module accepts a caller-supplied tenant parameter in create_client(tenant=...). Prior to version 0.50.0, the tenant parameter was not validated before being used to construct filesystem paths for secret resolution. A value containing path traversal sequences (for example, attacker-corp/../victim-corp) could cause the resolved path to escape the intended directory and access another tenant's secrets under:Plain Text/etc/secrets/appfnd/hana-agent-memory/<tenant>/Successful exploitation could allow unauthorized access to another tenant's mounted credentials, including OAuth client IDs and client secrets. This vulnerability could enable cross-tenant access to sensitive credentials.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-120013 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120013 is a high-severity vulnerability in SAP_SE SAP Cloud SDK for Python, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120013 in the wild and no public exploit code.

Affected product: SAP_SE SAP Cloud SDK for Python. 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-120013/ (Markdown: https://insights.sbomify.com/CVE-2026-120013/index.md)
```

## Sources

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

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