Tag: Migration Failure

Errors caused by failed or skipped database migrations

ID	Title	Description	Category	Technology	Tags
CRE-2025-0078 High Impact: 10/10 Mitigation: 2/10	SpiceDB Database Schema Failures: Missing Core Tables	Detects 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 Systems	spicedb	SpiceDB Migration Failure Schema Error PostgreSQL
CRE-2025-0135 Medium Impact: 7/10 Mitigation: 6/10	Supabase Self-Hosted: Database Migration Failures Due to SQL Syntax Errors	Detects when Supabase database migrations fail due to SQL syntax errors, invalid schema changes, or constraint violations. Migration failures can leave the database in an inconsistent state and prevent the application from starting or functioning properly.	migration-failure	postgresql	Supabase PostgreSQL Migration Failure Schema Error Self-Hosted Configuration Public
CRE-2025-0141 High Impact: 10/10 Mitigation: 7/10	Supabase Self-Hosted: Disk Full During Database Migration Operations	Detects when Supabase PostgreSQL database operations fail due to insufficient disk space during migrations, data imports, or large transactions. This can corrupt the database, leave migrations in inconsistent state, and cause complete service failure requiring manual intervention.	Storage	supabase	Supabase PostgreSQL Disk Full Storage Migration Failure WAL Self-Hosted Critical Failure Data Loss Risk Public