CVE-2026-69183

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Monkeytype is a minimalistic and customizable typing test. In 26.26.0 and earlier, the backend rate-limit key generator in backend/src/middlewares/rate-limit.ts uses client-controlled cf-connecting-ip and x-forwarded-for headers before the trust-proxy-derived req.ip value. An unauthenticated attacker can rotate either header to create a new bucket for each request, bypassing rootRateLimiter, badAuthRateLimiter, getKey(), and the getKeyWithUid() fallback used by public endpoints. This permits repeated POST /users/forgotPasswordEmail and verificationEmail requests, mail bombing registered users, consuming Firebase or SMTP quota, evading brute-force protection, and enabling resource exhaustion. Exploitability of cf-connecting-ip depends on deployment topology, but x-forwarded-for and direct-to-origin paths remain affected when those values are not overwritten by a trusted proxy. No fixed version is available as of this review.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Rate-limit and anti-brute-force controls bypassable via spoofed HTTP headers (forgotPasswordEmail/verificationEmail mail bombing and badAuth bypass) · Advisory · monkeytypegame/monkeytype · GitHub

https://github.com/monkeytypegame/monkeytype/security/advisories/GHSA-c878-p3jh-mmjf

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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-08-25 13:59 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:42 UTCEG score recompute
  4. 2026-08-23 03:46 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 04:30 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 05:12 UTCEG score recompute
  9. 2026-08-20 17:34 UTCEG score recompute
  10. 2026-08-20 17:17 UTCEG score recompute
  11. 2026-08-20 16:33 UTCEG score recompute
  12. 2026-08-20 16:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69183?
CVE-2026-69183 is a high vulnerability published on August 20, 2026. Monkeytype is a minimalistic and customizable typing test. In 26.26.0 and earlier, the backend rate-limit key generator in backend/src/middlewares/rate-limit.ts uses client-controlled cf-connecting-ip and x-forwarded-for headers before the trust-proxy-derived req.ip value. An unauthenticated…
When was CVE-2026-69183 disclosed?
CVE-2026-69183 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69183 actively exploited?
CVE-2026-69183 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 80.7% of all scored CVEs.
What is the CVSS score of CVE-2026-69183?
CVE-2026-69183 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-69183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69183, 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-69183

Explore →

Is Your Infrastructure Affected by CVE-2026-69183?

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

Start Free Scan →Browse All CVEs