# CVE-2025-36252: TS4500 Tape Library Insufficient Session Expiration

> An authenticated user can impersonate another user due to insufficient session expiration in IBM TS4500 Tape Library firmware.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-hm74-hhr5-rw72

## What is CVE-2025-36252?

CVE-2025-36252 is a medium-severity authentication bypass vulnerability in IBM Storage TS4500 Library, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Storage TS4500 Library 1.1.1.6 through 1.12.0.3 IBM TS4500 Tape Library/Diamondback Tape Library does not invalidate session which could allow an authenticated user to impersonate another user on the system.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-36252?


## How do I fix CVE-2025-36252?

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

## Is CVE-2025-36252 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36252 and fix it if it is affected.

What it is: CVE-2025-36252 is a medium-severity authentication bypass vulnerability in IBM Storage TS4500 Library, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36252 in the wild and no public exploit code.

Affected product: IBM Storage TS4500 Library. 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-2025-36252/ (Markdown: https://insights.sbomify.com/CVE-2025-36252/index.md)
```

## Sources

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

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