Skip to main content

Technology: spicedb

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0078
High
Impact: 10/10
Mitigation: 2/10
SpiceDB Database Schema Failures: Missing Core TablesDetects critical SpiceDB database schema failures caused by missing core tables like `metadata`, `alembic_version`, or `relation_tuple_transaction`. These errors often stem from incomplete migrations, startup race conditions, or schema corruption, resulting in a complete breakdown of SpiceDB authorization capabilities.Authorization SystemsspicedbSpiceDBMigration FailureSchema ErrorPostgreSQL
CRE-2025-0085
High
Impact: 8/10
Mitigation: 7/10
SpiceDB Schema Validation Failures Block Authorization UpdatesDetects SpiceDB schema validation failures that prevent authorization logic updates and deployments. These failures occur when invalid schema definitions are submitted, including syntax errors, circular dependencies, type conflicts, or malformed permission expressions, blocking critical authorization system updates.Authorization ProblemsspicedbSpiceDBAuthorizationConfigurationValidationCrashStartup Failure
CRE-2025-0105
High
Impact: 9/10
Mitigation: 3/10
SpiceDB Datastore Startup FailureDetects critical failures where a SpiceDB instance cannot start due to an invalid schema or an uninitialized datastore during the bootstrap process. This is a common configuration error that prevents the service from initializing and serving requests, leading to a total service outage.Authorization SystemsspicedbSpiceDBAuthorizationDatastoreMisconfigurationStartup Failure