Account compromise via unthrottled login attempts
Published Aug 18, 2026 · Updated Aug 19, 2026
Improper restriction of excessive authentication attempts in Karakeep before 0.33.0 allows remote attackers to brute-force passwords via the credential login endpoint. The NextAuth CredentialsProvider authorize() handler in apps/web/server/auth.ts calls validatePassword() directly and, before the fix, applied no rate limiting, lockout, CAPTCHA, or backoff to repeated failed logins. Exposure requires the password-based login path to be reachable; attackers who know or can enumerate an email address can automate online guessing until a weak or reused password yields account access.
Summary
What happened
Improper restriction of excessive authentication attempts in Karakeep before 0.33.0 allows remote attackers to brute-force passwords via the credential login endpoint. The NextAuth CredentialsProvider authorize() handler in apps/web/server/auth.ts calls validatePassword() directly and, before the fix, applied no rate limiting, lockout, CAPTCHA, or backoff to repeated failed logins. Exposure requires the password-based login path to be reachable; attackers who know or can enumerate an email address can automate online guessing until a weak or reused password yields account access.
The record
- CVE
- CVE-2026-75773
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Localhost Labs Ltd
- Product
- Karakeep
- Classifications
- CWE-307, CWE-799, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1
- Affected versionversion=0.10
- Affected versionversion=0.11
- Affected versionversion=0.12
- Affected versionversion=0.13
- Affected versionversion=0.14
- Affected versionversion=0.15
- Affected versionversion=0.16
- Affected versionversion=0.17
- Affected versionversion=0.18
- Affected versionversion=0.19
- Affected versionversion=0.2
- Affected versionversion=0.20
- Affected versionversion=0.21
- Affected versionversion=0.22
- Affected versionversion=0.23
- Affected versionversion=0.24
- Affected versionversion=0.25
- Affected versionversion=0.26
- Affected versionversion=0.27
- Affected versionversion=0.28
- Affected versionversion=0.29
- Affected versionversion=0.3
- Affected versionversion=0.30
- Affected versionversion=0.31
- Affected versionversion=0.32.0
- Affected versionversion=0.4
- Affected versionversion=0.5
- Affected versionversion=0.6
- Affected versionversion=0.7
- Affected versionversion=0.8
- Affected versionversion=0.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Missing Brute-Force Protection PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo