cve.bz

CVE-2025-65111 authzed spicedb: Insecure Inherited Permissions

2.9 lowEPSS 0.2%Fix available

Low (2.9) in authzed spicedb. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/authzed/spicedb 1.47.1.

On this page
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.

Severity

CVSS 4.0

2.9 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-11-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-277 Insecure Inherited Permissions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-65111 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65111?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65111?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65111 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
authzed:spicedbbefore 1.47.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9m7r-g8hg-x3vrGogithub.com/authzed/spicedb<1.47.11.47.1
GO-2025-4151Gogithub.com/authzed/spicedb<1.47.11.47.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20251209T172047-150000.1.127.1SUSE-SU-2025:4395-1
openSUSELeap 15.6govulncheck-vulndb0.0.20251209T172047-150000.1.127.1SUSE-SU-2025:4395-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

References

Check your stackJSON