# CVE-2025-63909: Privilege escalation in n/a

> Attackers can escalate privileges to root and read or write arbitrary files via incorrect access control in the TapeDumper component.

- **Severity:** High 7.2 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-9xwp-q52p-3g5c

## What is CVE-2025-63909?

CVE-2025-63909 is a high-severity vulnerability in n/a, published on 3 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Incorrect access control in the component /opt/SRLtzm/bin/TapeDumper of Cohesity TranZman Migration Appliance Release 4.0 Build 14614 allows attackers to escalate privileges to root and read and write arbitrary files.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Cohesity Tranzman.

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

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

## Is CVE-2025-63909 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63910](https://insights.sbomify.com/CVE-2025-63910/): File upload in n/a (high 7.2)
- [CVE-2025-63911](https://insights.sbomify.com/CVE-2025-63911/): Command injection in n/a (high 7.2)
- [CVE-2025-67840](https://insights.sbomify.com/CVE-2025-67840/): Command injection in n/a (high 7.2)
- [CVE-2025-63912](https://insights.sbomify.com/CVE-2025-63912/): Weak cryptography in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63909 is a high-severity vulnerability in n/a, published on 3 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63909 in the wild and no public exploit code.

Affected product: n/a. 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-63909/ (Markdown: https://insights.sbomify.com/CVE-2025-63909/index.md)
```

## Sources

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

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