CVE-2026-46649
9.1laurent22 · Joplin
Joplin Server prior to 3.7.2 lacks rate limiting on the SSO login endpoint, allowing unauthenticated attackers to brute-force authentication codes and gain unauthorized access to user accounts.
Executive summary
A critical authentication bypass vulnerability in Joplin Server allows unauthenticated attackers to gain full account access via brute-force attacks against the SSO login process.
Vulnerability
The vulnerability exists in the GET /api/login_with_code/:id endpoint, which fails to implement brute-force protection for nine-digit SSO authentication codes. An unauthenticated attacker can exhaust the codes within their ten-minute lifetime to hijack user sessions.
Business impact
Successful exploitation allows an attacker to obtain a full session token, granting them complete control over the victim's notes, notebooks, and account settings. Given the CVSS score of 9.1, this vulnerability poses a severe risk to data confidentiality and integrity, potentially leading to unauthorized disclosure of sensitive information stored within the application.
Remediation
Immediate Action: Upgrade Joplin Server to version 3.7.2 or later to implement the necessary brute-force rate limiting on the SSO authentication endpoint.
Proactive Monitoring: Review server access logs for anomalous patterns of requests to the /api/login_with_code/ endpoint, specifically looking for high volumes of failed attempts originating from single or distributed IP addresses.
Compensating Controls: Deploy a Web Application Firewall (WAF) or rate-limiting proxy in front of the Joplin Server instance to detect and block excessive requests to the login API.
Exploitation status
Public Exploit Available: No
Analyst recommendation
The severity of this vulnerability, combined with its direct impact on user account security, necessitates immediate action. Administrators should prioritize the update to version 3.7.2 across all production instances to close the authentication gap and prevent unauthorized access to sensitive user data.
More laurent22 CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief critical section