Permission denial via incomplete caveated branch evaluation
Published Jun 6, 2025 · Updated Jun 6, 2025
Improper security checking in AuthZed SpiceDB before 1.44.2 allows remote attackers to receive false permission denials. In internal/graph/check.go, checkTupleToUserset fails to require all branch results when incoming caveats exist, so one caveated branch prematurely determines the result. The affected path requires an arrow over a caveated relation and multiple caveated branches; a valid request can be denied but cannot grant unauthorized access.
Summary
What happened
Improper security checking in AuthZed SpiceDB before 1.44.2 allows remote attackers to receive false permission denials. In internal/graph/check.go, checkTupleToUserset fails to require all branch results when incoming caveats exist, so one caveated branch prematurely determines the result. The affected path requires an arrow over a caveated relation and multiple caveated branches; a valid request can be denied but cannot grant unauthorized access.
The record
- CVE
- CVE-2025-49011
- Published
- Jun 6, 2025
- Updated
- Jun 6, 2025
- Vendor
- AuthZed
- Product
- SpiceDB
- Classifications
- CWE-358
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Jun 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.44.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream caveated-branch reproduction caseproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo