# CVE-2024-13975: Commvault 11.20.0 - 11.36.0 Windows Access Nodes Compromise via Local File Server Agent Abuse

> Local attackers with file server agent access can compromise Windows access nodes, enabling lateral movement in backup infrastructure.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2025
- **Updated:** 22 Nov 2025
- **Also known as:** GHSA-9mcx-q5wv-mpmg

## What is CVE-2024-13975?

CVE-2024-13975 is a high-severity vulnerability in Commvault, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local privilege escalation vulnerability exists in Commvault for Windows versions 11.20.0, 11.28.0, 11.32.0, 11.34.0, and 11.36.0. In affected configurations, a local attacker who owns a client system with the file server agent installed can compromise any assigned Windows access nodes. This may allow unauthorized access or lateral movement within the backup infrastructure. The issue has been resolved in versions 11.32.60, 11.34.34, and 11.36.8.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-13975?


## How do I fix CVE-2024-13975?

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

## Is CVE-2024-13975 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13975 and fix it if it is affected.

What it is: CVE-2024-13975 is a high-severity vulnerability in Commvault, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13975 in the wild and no public exploit code.

Affected product: Commvault. 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-2024-13975/ (Markdown: https://insights.sbomify.com/CVE-2024-13975/index.md)
```

## Sources

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

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