# CVE-2025-21120: Missing authorization in Avamar Server

> A low-privileged remote attacker can exploit improper HTTP permission handling in Dell Avamar to expose sensitive information.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 4 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qjvg-gx5p-355w

## What is CVE-2025-21120?

CVE-2025-21120 is a high-severity missing authorization vulnerability in Dell Avamar Server, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dell Avamar, versions prior to 19.10 SP1 with patch 338904, contains a Trusting HTTP Permission Methods on the Server-Side vulnerability in Security. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information exposure.

Weakness: CWE-650 (Trusting HTTP Permission Methods on the Server Side)

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

It affects 1 product.


Products: Dell Avamar.

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

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

## Is CVE-2025-21120 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21120 is a high-severity missing authorization vulnerability in Dell Avamar Server, published on 4 Aug 2025. 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-21120 in the wild and no public exploit code.

Affected product: Dell Avamar Server. 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-21120/ (Markdown: https://insights.sbomify.com/CVE-2025-21120/index.md)
```

## Sources

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

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