CVE-2026-31863

CVE-2026-31863 is a low-severity security vulnerability in github.com/anyproto/anytype-heart (go), affecting versions < 0.48.4. It is fixed in 0.48.4, 0.1.11.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Anytype Heart's gRPC API client challenge verification can be bypassed on localhost

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.

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.

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.

CVE-2026-31863 has a CVSS score of 3.6 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.48.4, 0.1.11); upgrading removes the vulnerable code path.

Affected versions

github.com/anyproto/anytype-heart (< 0.48.4) github.com/anyproto/anytype-cli (< 0.1.11)

Security releases

github.com/anyproto/anytype-heart → 0.48.4 (go) github.com/anyproto/anytype-cli → 0.1.11 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Frequently Asked Questions

  1. What is CVE-2026-31863? CVE-2026-31863 is a low-severity security vulnerability in github.com/anyproto/anytype-heart (go), affecting versions < 0.48.4. It is fixed in 0.48.4, 0.1.11.
  2. How severe is CVE-2026-31863? CVE-2026-31863 has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2026-31863?
    • github.com/anyproto/anytype-heart (go) (versions < 0.48.4)
    • github.com/anyproto/anytype-cli (go) (versions < 0.1.11)
  4. Is there a fix for CVE-2026-31863? Yes. CVE-2026-31863 is fixed in 0.48.4, 0.1.11. Upgrade to this version or later.
  5. Is CVE-2026-31863 exploitable, and should I be worried? Whether CVE-2026-31863 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-31863 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-31863?
    • Upgrade github.com/anyproto/anytype-heart to 0.48.4 or later
    • Upgrade github.com/anyproto/anytype-cli to 0.1.11 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo