Local gRPC API access without challenge code
Published Mar 11, 2026 · Updated Mar 11, 2026
Authentication bypass in Anytype Heart before 0.48.4 allows local users to access the local gRPC client API without the 4-digit code. Challenge verification accepts a client without the correct code, but the vendor has not disclosed the underlying verification error. Exploitation requires user-level access, discovery of a randomized localhost port, and a running Desktop or CLI instance; it permits data access and modification but not service interruption.
Summary
What happened
Authentication bypass in Anytype Heart before 0.48.4 allows local users to access the local gRPC client API without the 4-digit code. Challenge verification accepts a client without the correct code, but the vendor has not disclosed the underlying verification error. Exploitation requires user-level access, discovery of a randomized localhost port, and a running Desktop or CLI instance; it permits data access and modification but not service interruption.
The record
- CVE
- CVE-2026-31863
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Any Association
- Product
- Anytype Heart
- Classifications
- CWE-307
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 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.48.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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