Skip to content

← Actionable
Low, CVSS 3.6

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

CVE-2026-31863GHSA-vv3h-7qwr-722v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/anyproto/anytype-heart 0.48.4; github.com/anyproto/anytype-cli 0.1.11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.6 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-31863: 0.11% estimated exploitation activity in the next 30 days; percentile 1.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-vv3h-7qwr-722v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31863

Advisory: Anytype Heart's gRPC API client challenge verification can be bypassed on localhost
IDs: CVE-2026-31863, GHSA-vv3h-7qwr-722v
Record: https://patchnext.com/advisories/cve-2026-31863 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/anyproto/anytype-heart 0.48.4; github.com/anyproto/anytype-cli 0.1.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/anyproto/anytype-heart: affected < 0.48.4; fixed in 0.48.4
- Go github.com/anyproto/anytype-cli: affected < 0.1.11; fixed in 0.1.11

## Suggested inspection (read-only)
- Go github.com/anyproto/anytype-heart: check the installed version with your package manager.
- Go github.com/anyproto/anytype-cli: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/anyproto/anytype-heart, github.com/anyproto/anytype-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vv3h-7qwr-722v (GitHub-reviewed advisory GHSA-vv3h-7qwr-722v lists affected ranges: Go github.com/anyproto/anytype-heart >=0 =0 <0.1.11)

Commands are suggestions: review each one before running it.

Loading voting…