# CVE-2021-32088: An issue was discovered in Quest KACE Systems Deployment Appliance (SMA) 11.0.273.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-wr85-vcm8-q7f4

## What is CVE-2021-32088?

CVE-2021-32088 is a critical vulnerability in n/a, published on 27 Jul 2026. 

### Official description

An issue was discovered in Quest KACE Systems Deployment Appliance (SMA) 11.0.273. Certain API endpoints contain a rate-limiting feature to minimize a brute-force attack. This protection can be bypassed by removing the kboxid cookie.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2021-32088?

It affects 1 product.


Products: Quest Kace Systems Management Appliance.

## How do I fix CVE-2021-32088?

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

## Is CVE-2021-32088 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-32975](https://insights.sbomify.com/CVE-2025-32975/): Quest KACE Systems Management Appliance (SMA) Improper Authentication (critical 10.0, exploited in the wild)
- [CVE-2021-32084](https://insights.sbomify.com/CVE-2021-32084/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-32086](https://insights.sbomify.com/CVE-2021-32086/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-29807](https://insights.sbomify.com/CVE-2022-29807/): SQL injection in n/a (critical 9.8)
- [CVE-2022-30285](https://insights.sbomify.com/CVE-2022-30285/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32088 and fix it if it is affected.

What it is: CVE-2021-32088 is a critical vulnerability in n/a, published on 27 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2021-32088 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-2021-32088/ (Markdown: https://insights.sbomify.com/CVE-2021-32088/index.md)
```

## Sources

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

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