# CVE-2026-92583: AVideo through 29.0 Rate Limit Bypass via Non-Atomic Counter Increment

> Attackers can bypass login rate limits via a race condition in AVideo, enabling brute-force attacks against user credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-52g5-jg96-428j, GHSA-8jrm-qg5f-966w

## What is CVE-2026-92583?

CVE-2026-92583 is a medium-severity vulnerability in WWBN AVideo, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo through 29.0 contains a race condition in the enforceRateLimit() function that fails to atomically increment rate limit counters, allowing attackers to bypass all rate limits including login brute-force protection by issuing concurrent requests. Attackers can submit parallel credential attempts to exceed the documented 30-attempts-per-5-minutes login limit by an arbitrary factor determined only by their connection concurrency.

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

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


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

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

## Is CVE-2026-92583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92583 is a medium-severity vulnerability in WWBN AVideo, published on 16 Sep 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-92583 exists.

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

## Sources

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

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