CVE-2025-49011VulnerabilityPublished 6 Jun 2025

CVE-2025-49011: authzed spicedb · Improperly Implemented Security Check for Standard

Affects authzed spicedbSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low : upgrade to 1.44.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.44.2

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade authzed/spicedb to 1.44.2.

Affected software

Product	Affected	Fixed in
GitHubauthzed/spicedb`pkg:github/authzed/spicedb`Other threats	Affected <1.44.2	Fixed in 1.44.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should promptly upgrade SpiceDB to version 1.44.2 or later to remediate this vulnerability. Until the upgrade is feasible, schema designers should avoid using caveats on arrow’ed relations to prevent triggering the faulty permission evaluation logic. Additionally, organizations should audit their authorization schemas to identify and refactor any caveated arrow’ed relations. Implementing comprehensive testing of authorization logic after schema changes can help detect unexpected permission denials early. Monitoring application logs for unusual access denials related to authorization checks can provide early indicators of this issue. Finally, organizations should maintain an updated inventory of systems using SpiceDB to ensure all instances are patched in a timely manner.

Description

SpiceDB is an open source database for storing and querying fine-grained authorization data. Prior to version 1.44.2, 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. Version 1.44.2 fixes the issue. As a workaround, do not use caveats in the schema over an arrow’ed relation.

Impact

For European organizations utilizing SpiceDB for authorization management, this vulnerability could cause legitimate permission checks to fail, resulting in denial of access to authorized users or services. While this does not directly lead to unauthorized data access or system compromise, it can disrupt business operations, especially in environments where fine-grained access control is critical, such as financial services, healthcare, or government sectors. The integrity impact is low but non-negligible, as incorrect permission denials can affect workflow continuity, user productivity, and potentially lead to operational delays. Given the network-exploitable nature but high attack complexity and no need for privileges or user interaction, the risk of widespread exploitation is limited. However, organizations relying heavily on caveated relations in their authorization schemas are more susceptible to operational disruptions until they apply the patch or implement the recommended workaround.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 11:27 UTC

WeaknessesCWE-358

Technical details

References

Community reviews

Related threats