A vulnerability was found in karakeep-app karakeep up to 0.32.0. The affected element is the function authorize of the file apps/web/server/auth.ts of the component Login Endpoint. The manipulation results in improper restriction of excessive authentication attempts. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is described as difficult. The exploit has been made public and could be used. Upgrading to version 0.33.0 is sufficient to fix this issue. The patch is identified as f7d042971d0d2bcc7119654830cf1eb93eabbf24. It is advisable to upgrade the affected component.
CVE-2026-75773
Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-08-18. a secondary CVSS source baseline 3.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 20, 2026
References (8)
- cna@vuldbhttps://github.com/karakeep-app/karakeep/
- cna@vuldbhttps://github.com/karakeep-app/karakeep/commit/f7d042971d0d2bcc7119654830cf1eb93eabbf24
- cna@vuldbhttps://github.com/karakeep-app/karakeep/issues/2919
- cna@vuldbhttps://github.com/karakeep-app/karakeep/releases/tag/mcp/v0.33.0
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-75773
- cna@vuldbhttps://vuldb.com/submit/877731
- cna@vuldbhttps://vuldb.com/vuln/391519
- cna@vuldbhttps://vuldb.com/vuln/391519/cti
Vendor Advisories for CVE-2026-75773(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:59 UTCEG score recompute
- 2026-08-20 12:59 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:27 UTCEG score recompute
- 2026-08-19 14:27 UTCGHSA enrichment
- 2026-08-19 14:23 UTCNVD updateCVSS v4 → 2.9
- 2026-08-19 13:59 UTCEG score recompute
- 2026-08-19 13:59 UTCGHSA enrichment
- 2026-08-19 13:57 UTCMITRE cvelistV5CVSS v4 → 6.3
- 2026-08-18 11:23 UTCEG score recompute
- 2026-08-18 11:22 UTCNVD updateCVSS v4 → 2.9
- 2026-08-18 11:07 UTCEG score recompute
- 2026-08-18 11:03 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75773?
When was CVE-2026-75773 disclosed?
Is CVE-2026-75773 actively exploited?
What is the CVSS score of CVE-2026-75773?
How do I remediate CVE-2026-75773?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75773
Is Your Infrastructure Affected by CVE-2026-75773?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.