CVE-2025-65111 SpiceDB's LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results

Low 2.9 Published Updated

SpiceDB may return incomplete permission results for specific union schemas, potentially allowing unauthorized access to resources.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-65111?

CVE-2025-65111 is a low-severity vulnerability in authzed spicedb, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

SpiceDB is an open source database system for creating and managing security-critical application permissions. Prior to version 1.47.1, if a schema includes the following characteristics: permission defined in terms of a union (+) and that union references the same relation on both sides (but one side arrows to a different permission). Then SpiceDB may have missing LookupResources results when checking the permission. This only affects LookupResources; other APIs calculate permissionship correctly. The issue is fixed in version 1.47.1.

Weakness: CWE-277

Which versions are affected by CVE-2025-65111?

3 open source packages ship an affected version, including github.com/authzed/spicedb. It affects 1 product.

PackageAffectedFixed in
github.com/authzed/spicedb GoAll versions1.47.1
github.com/authzed/spicedb GoAll versions1.47.1
github.com/authzed/spicedb GoAll versions1.47.1

Products include Authzed Spicedb.

How do I fix CVE-2025-65111?

Upgrade github.com/authzed/spicedb to 1.47.1 or later.

Is CVE-2025-65111 being exploited?

There is no known exploitation of CVE-2025-65111 in the wild and no public exploit code.

Sources

Also known as GHSA-9m7r-g8hg-x3vr, GO-2025-4151.

Is CVE-2025-65111 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free