# CVE-2026-32295: JetKVM insufficient login rate limiting

> Attackers can brute-force credentials due to missing login rate limits, potentially taking over JetKVM accounts.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-g66j-37wx-vrj5

## What is CVE-2026-32295?

CVE-2026-32295 is a critical vulnerability in JetKVM, published on 17 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JetKVM before 0.5.4 does not rate limit login requests, enabling brute-force attempts to guess credentials.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-32295?

It affects 1 product.


Products: Jetkvm Kvm.

## How do I fix CVE-2026-32295?

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

## Is CVE-2026-32295 being exploited?

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

## Other vulnerabilities in JetKVM

- [CVE-2026-32294](https://insights.sbomify.com/CVE-2026-32294/): JetKVM insufficient firmware verification (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32295 and fix it if it is affected.

What it is: CVE-2026-32295 is a critical vulnerability in JetKVM, published on 17 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32295 exists.

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

## Sources

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

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