# CVE-2025-32977: File upload in n/a

> Unauthenticated attackers can upload malicious backup files due to weak signature validation, potentially compromising system integrity and executing code.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-79hg-66hr-6j93

## What is CVE-2025-32977?

CVE-2025-32977 is a critical vulnerability in n/a, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Quest KACE Systems Management Appliance (SMA) 13.0.x before 13.0.385, 13.1.x before 13.1.81, 13.2.x before 13.2.183, 14.0.x before 14.0.341 (Patch 5), and 14.1.x before 14.1.101 (Patch 4) allows unauthenticated users to upload backup files to the system. While signature validation is implemented, weaknesses in the validation process can be exploited to upload malicious backup content that could compromise system integrity.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2025-32977 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32977 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32977 is a critical vulnerability in n/a, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32977 exists.

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-32977/ (Markdown: https://insights.sbomify.com/CVE-2025-32977/index.md)
```

## Sources

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

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