# CVE-2025-32976: Auth bypass in n/a

> Authenticated users can bypass TOTP-based two-factor authentication to gain elevated access on Quest KACE SMA appliances.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Jun 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-m359-p2w2-2pxh

## What is CVE-2025-32976?

CVE-2025-32976 is a high-severity authentication bypass vulnerability in n/a, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### 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) contains a logic flaw in its two-factor authentication implementation that allows authenticated users to bypass TOTP-based 2FA requirements. The vulnerability exists in the 2FA validation process and can be exploited to gain elevated access.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-32976 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32976 is a high-severity authentication bypass vulnerability in n/a, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32976 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-32976/ (Markdown: https://insights.sbomify.com/CVE-2025-32976/index.md)
```

## Sources

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

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