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.5% (39th percentile of EPSS-scored CVEs). 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
Elevated
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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

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.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 20, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. No fix on record yet. Sources: github.
githubMentions a patch (unverified)🟡 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 11× in last 7d / 48× 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-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-08 05:28 UTCEG score recompute
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 19:31 UTCEG score recompute
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-06 07:53 UTCEG score recompute
  8. 2026-10-05 17:43 UTCEPSS rescore
  9. 2026-10-05 05:01 UTCEG score recompute
  10. 2026-10-04 23:22 UTCEPSS rescore
  11. 2026-10-03 16:48 UTCEG score recompute
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-02 21:00 UTCEG score recompute
  14. 2026-10-02 17:56 UTCEPSS rescore
  15. 2026-10-01 21:30 UTCEG score recompute
  16. 2026-10-01 19:50 UTCEPSS rescore
  17. 2026-09-30 20:31 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-30 08:17 UTCEG score recompute
  20. 2026-09-28 21:38 UTCEG score recompute
  21. 2026-09-28 13:52 UTCEPSS rescore
  22. 2026-09-27 15:58 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-27 03:15 UTCEG score recompute
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 62 more
  1. 2026-09-24 19:26 UTCEG score recompute
  2. 2026-09-23 20:05 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 19:46 UTCEG score recompute
  5. 2026-09-22 07:37 UTCEG score recompute
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-20 20:40 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-19 19:37 UTCEG score recompute
  10. 2026-09-18 20:20 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 21:23 UTCEG score recompute
  13. 2026-09-16 21:44 UTCEG score recompute
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 09:43 UTCEG score recompute
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 10:14 UTCEG score recompute
  18. 2026-09-13 23:10 UTCEG score recompute
  19. 2026-09-12 23:54 UTCEG score recompute
  20. 2026-09-12 00:37 UTCEG score recompute
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 12:59 UTCEG score recompute
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 13:42 UTCEG score recompute
  25. 2026-09-09 01:59 UTCEG score recompute
  26. 2026-09-08 22:01 UTCEPSS rescore
  27. 2026-09-07 19:50 UTCEG score recompute
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-06 20:26 UTCEG score recompute
  30. 2026-09-06 13:47 UTCEPSS rescore
  31. 2026-09-05 21:08 UTCEG score recompute
  32. 2026-09-05 15:31 UTCEPSS rescore
  33. 2026-09-04 21:50 UTCEG score recompute
  34. 2026-09-04 09:58 UTCEG score recompute
  35. 2026-09-04 05:07 UTCEPSS rescore
  36. 2026-09-02 22:09 UTCEG score recompute
  37. 2026-09-02 14:12 UTCEPSS rescore
  38. 2026-09-01 22:43 UTCEG score recompute
  39. 2026-09-01 13:54 UTCEPSS rescore
  40. 2026-09-01 11:04 UTCEG score recompute
  41. 2026-09-01 04:40 UTCEPSS rescore
  42. 2026-08-31 00:04 UTCEG score recompute
  43. 2026-08-30 19:17 UTCEPSS rescore
  44. 2026-08-30 12:26 UTCEG score recompute
  45. 2026-08-30 01:22 UTCEPSS rescore
  46. 2026-08-29 01:29 UTCEG score recompute
  47. 2026-08-28 21:42 UTCEPSS rescore
  48. 2026-08-28 00:12 UTCEG score recompute
  49. 2026-08-27 00:55 UTCEG score recompute
  50. 2026-08-26 14:47 UTCEPSS rescore
  51. 2026-08-25 13:59 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescore
  53. 2026-08-24 14:42 UTCEG score recompute
  54. 2026-08-23 03:46 UTCEG score recompute
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 04:30 UTCEG score recompute
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-21 05:12 UTCEG score recompute
  59. 2026-08-20 17:34 UTCEG score recompute
  60. 2026-08-20 17:17 UTCEG score recompute
  61. 2026-08-20 16:33 UTCEG score recompute
  62. 2026-08-20 16:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 on August 20, 2026, with the most recent update on September 18, 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.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69183?
CVE-2026-69183 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69183?
No fix for CVE-2026-69183 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

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.

Book a Demo →Browse All CVEs