How severe is GHSA-vv3h-7qwr-722v?

GHSA-vv3h-7qwr-722v has a CVSS score of 3.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vv3h-7qwr-722v?

GHSA-vv3h-7qwr-722v affects the following packages: github.com/anyproto/anytype-heart (Go), github.com/anyproto/anytype-cli (Go). Ecosystems affected: Go.

How do I fix GHSA-vv3h-7qwr-722v?

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 GHSA-vv3h-7qwr-722v is resolved across your whole dependency graph.

How do I detect GHSA-vv3h-7qwr-722v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/anyproto/anytype-heart. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-vv3h-7qwr-722v if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-vv3h-7qwr-722v?

O3 pinpoints whether GHSA-vv3h-7qwr-722v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-vv3h-7qwr-722v actively exploited in the wild?

No public exploit code has been indexed for GHSA-vv3h-7qwr-722v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vv3h-7qwr-722v?

GHSA-vv3h-7qwr-722v has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 1th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vv3h-7qwr-722v?

GHSA-vv3h-7qwr-722v is classified as CWE-307 (CWE-307). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vv3h-7qwr-722v published, and has it been updated?

GHSA-vv3h-7qwr-722v was published on March 11, 2026 and was last updated on March 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-vv3h-7qwr-722v

LOW

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

Also known asCVE-2026-31863GO-2026-4680

Published

Mar 11, 2026

Updated

Mar 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk1th percentile+0.08%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐹github.com/anyproto/anytype-heart🐹github.com/anyproto/anytype-cli

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/anyproto/anytype-heart`	all versions	0.48.4
🐹Go	`github.com/anyproto/anytype-cli`	all versions	0.1.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/anyproto/anytype-heart. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-vv3h-7qwr-722v 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.
How O3 protects you
O3 pinpoints whether GHSA-vv3h-7qwr-722v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vv3h-7qwr-722v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

#### 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 A

O3 Security · Impact-Aware SCA

Is GHSA-vv3h-7qwr-722v in your dependencies?

O3 detects GHSA-vv3h-7qwr-722v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-vv3h-7qwr-722v

EPSS Exploitation Probability

Blast Radius

Description

Impact

Exploitation requires:

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-vv3h-7qwr-722v in your dependencies?