Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-49011 — spicedb

🟢 CVSS 3.7 — Low ✅ No Known Exploit CWE-358 NVD
3.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

SpiceDB checks involving relations with caveats can result in no permission when permission is expected

Impact

On schemas involving arrows with caveats on the arrow’ed relation, when the path to resolve a CheckPermission request involves the evaluation of multiple caveated branches, requests may return a negative response when a positive response is expected.

For example, given this schema:

```

definition user {}

definition office {

relation parent: office

relation manager: user

permission read = manager + parent->read

}

definition group {

relation parent: office

permission read = parent->read

}

definition document {

relation owner: group with equals

permission read = owner->read

}

caveat equals(actual string, required string) {

actual == required

}

```

and these relationships:

```

office:headoffice#manager@user:maria

office:branch1#parent@office:headoffice

group:admins#parent@office:branch1

group:managers#parent@office:headoffice

document:budget#owner@group:admins[equals:{"required":"admin"}]

document:budget#owner@group:managers[equals:{"required":"manager"}]

```

Permission for 'document:budget#read@user:maria with {"actual" : "admin"}' is returned as NO_PERMISSION when HAS_PERMISSION is the correct answer.

Patches

Upgrade to v1.44.2.

Workarounds

Do not use caveats in your schema over an arrow’ed relation.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2025-49011 is classified as CWE-358: Improperly Implemented Security Check for Standard. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.

Affected software

CVE-2025-49011 is recorded against 2 packages.

  • github.com/authzed/spicedb
  • spicedb (fixed in 1.44.2)

Timeline and source

Published on 6 June 2025 and last revised on 3 March 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

github.com/authzed/spicedb has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-358: Improperly Implemented Security Check for Standard) in other software:

Details

Severity LOW
CVSS Score 3.7
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CWE CWE-358
Public Exploit ✅ No
Source NVD
Published 2025-06-06
Updated 2026-08-20
Modified 2026-03-03

Affected Packages

Software From version Fixed in
github.com/authzed/spicedb — —
spicedb — 1.44.2

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2025-49011?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2025-49011 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓