CVE-2026-31863 — anytype-heart
LOWCVE-2026-31863 is a low-severity (CVSS 3.6) CWE-307 vulnerability in github.com/anyproto/anytype-heart. A fix is available for github.com/anyproto/anytype-heart — see the affected versions and patch details below.
Improper Restriction of Excessive Authentication Attempts in github.com/anyproto/anytype-heart
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-31863.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/anyproto/anytype-heart🐹github.com/anyproto/anytype-cliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The challenge-based authentication for the local gRPC client API can be bypassed, allowing an attacker to gain access without the 4-digit code.
Affected components:
- Anytype Desktop (all platforms) ≤ v0.48.2
- Anytype-CLI (headless deployments) ≤ v0.1.9
Not affected:
- Anytype mobile apps (iOS, Android) - do not expose a local gRPC server
Who is impacted: This vulnerability is scoped to localhost. The gRPC and gRPC-Web ports bind to 127.0.0.1 only and are not exposed to the local network or internet.
Exploitation requires:
- Local user-level access to the machine running Anytype
- Discovery of the randomized listening port
- A running Anytype instance
Anytype-CLI headless deployments may be at higher risk only if an administrator has chosen to set up their own reverse proxy and configured it in a way that exposes gRPC or gRPC-Web ports to an external network. By default, these ports are not externally accessible and there is no built-in mechanism to expose them.
Patches
- anytype-heart library: v0.48.4
- Anytype Desktop: v0.54.5
- Anytype-CLI: v0.1.11
Workarounds
- Desktop users: No immediate action required. The vulnerability requires existing local access to the machine.
- Anytype-CLI administrators: If using a custom reverse proxy, ensure it does not expose gRPC or gRPC-Web ports to external networks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/anyproto/anytype-heart | all versions | 0.48.4go get github.com/anyproto/anytype-heart@v0.48.4 |
| 🐹Go | github.com/anyproto/anytype-cli | all versions | 0.1.11go get github.com/anyproto/anytype-cli@v0.1.11 |
Affected Products
anytype clianytypeanytype desktopanytypeanytype heartanytypeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/anyproto/anytype-heart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/anyproto/anytype-heart to 0.48.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-31863 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-31863 in your dependencies?
Find it across Go, including transitive dependencies.