Skip to content
Fencer Vulns
low 3.6

CVE-2026-31863 json

Improper Restriction of Excessive Authentication Attempts in github.com/anyproto/anytype-heart

published 2026-03-11 7 mo ago modified 2026-06-17 4 mo ago also GHSA-vv3h-7qwr-722v , GO-2026-4680 , EUVD-2026-11267

cvss
3.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/anyproto/anytype-heart 0.48.4
  • go github.com/anyproto/anytype-cli 0.1.11
  • anytype anytype_cli 0.1.11
  • anytype anytype_desktop 0.54.5
  • anytype anytype_heart 0.48.4
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1

suse advisories SUSE-SU-2026:1042-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 3.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/anyproto/anytype-heart
<0.48.4
0.48.4
go github.com/anyproto/anytype-cli
<0.1.11
0.1.11

Affected products

  • anyproto anytype-heart
  • anyproto anytype-cli
  • anyproto anytype-ts

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.