CVE-2025-65111

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-11-21 22:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-08 10:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 2.9 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-11-21 22:16 UTC

Last modified

2026-10-08 10:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-277

Record status

Analyzed

Affected

• Authzed Spicedb < 1.47.1

Attack profile CVSS 4.0 · 2.9

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-65111.md and follow it. Check whether this project is affected by CVE-2025-65111. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge