CVE-2026-92583

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-17. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
60(Attend)
EG Risk 60/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

AVideo through 29.0 Rate Limit Bypass via Non-Atomic Counter Increment | Advisories | VulnCheck

https://www.vulncheck.com/advisories/avideo-through-29.0-rate-limit-bypass-via-non-atomic-counter-increment
github Patch Available🟡 PoC Available

Identification and Authentication Failures: enforceRateLimit() is a non-atomic read-modify-write, so concurrent requests defeat every rate limit in AVideo, including the login brute-force cap · Advisory · WWBN/AVideo · GitHub

https://github.com/WWBN/AVideo/security/advisories/GHSA-8jrm-qg5f-966w

Vendor Advisories for CVE-2026-92583(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 16:22 UTCEG score recompute
  2. 2026-09-19 16:22 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 16:00 UTCEG score recompute
  5. 2026-09-18 16:00 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 15:23 UTCEG score recompute
  8. 2026-09-17 15:23 UTCGHSA enrichment
  9. 2026-09-17 14:59 UTCEG score recompute
  10. 2026-09-17 14:59 UTCGHSA enrichment
  11. 2026-09-16 22:26 UTCEG score recompute
  12. 2026-09-16 21:54 UTCEG score recompute
  13. 2026-09-16 21:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92583?
CVE-2026-92583 is a medium vulnerability published on September 16, 2026. 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…
When was CVE-2026-92583 disclosed?
CVE-2026-92583 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92583 actively exploited?
CVE-2026-92583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2026-92583?
CVE-2026-92583 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-92583?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92583, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92583

Explore →

Is Your Infrastructure Affected by CVE-2026-92583?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs