CVE-2026-31863: anyproto anytype-heart · Improper Restriction of Excessive Authentication Attempts
Affects anyproto anytype-heartSource CVE Database V5
Not known to be exploited · CVSS 3.6 Low : upgrade to 0.48.4 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.48.4, 0.1.11, 0.54.5
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade anytype-heart and anyproto/anytype-heart to 0.48.4; anytype-cli to 0.1.11; anytype-ts to 0.54.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| anyprotoanytype-heart | Affected
| Fixed in
|
| anyprotoanytype-cli | Affected
| Fixed in
|
| anyprotoanytype-ts | Affected
| Fixed in
|
GitHubanyproto/anytype-heartpkg:github/anyproto/anytype-heartOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-31863, organizations and users should immediately update anytype-heart to version 0.48.4 or later, anytype-cli to 0.1.11 or later, and Anytype Desktop to 0.54.5 or later, as these versions contain the fix for the authentication bypass. Beyond patching, it is critical to enforce strict local system access controls to prevent unauthorized users or processes from gaining local access to systems running Anytype components. Employ endpoint security solutions to detect and prevent malware or unauthorized local access attempts. Additionally, monitor local API access logs for unusual authentication attempts or bypass patterns. Consider implementing multi-factor authentication or additional layers of security around local API access if supported by Anytype in future releases. Regularly audit and restrict user privileges to minimize the risk of privilege escalation that could facilitate exploitation. Finally, maintain an up-to-date inventory of Anytype deployments to ensure all instances are patched promptly.
Description
Anytype Heart is the middleware library for Anytype. The challenge-based authentication for the local gRPC client API can be bypassed, allowing an attacker to gain access without the 4-digit code. This vulnerability is fixed in anytype-heart 0.48.4, anytype-cli 0.1.11, and Anytype Desktop 0.54.5.