Category: Database Problems

Problems related to databases, like MySQL, PostgreSQL, MongoDB, and others

ID	Title	Description	Category	Technology	Tags
CRE-2025-0035 Critical Impact: 7/10 Mitigation: 6/10	psycopg2 SSL error due to thread or forked process state	Applications using psycopg2 with OpenTelemetry instrumentation or threading may fail with SSL-related errors such as "decryption failed or bad record mac". This often occurs when a database connection is created before a fork or from an unsafe thread context, causing the SSL state to become invalid.	Database Problems	django	Ssl Psycopg2 Fork Threads Django Instrumentation Opentelemetry Known Issue Public
CRE-2025-0042 Critical Impact: 7/10 Mitigation: 5/10	PostgreSQL transaction fails with deadlock detected error in psycopg2 and Django	- Applications using Django with PostgreSQL and psycopg2 may encounter `deadlock detected` errors under concurrent write-heavy workloads. - PostgreSQL raises this error when two or more transactions block each other cyclically while waiting for locks, and one must be aborted. - Django surfaces this as an `OperationalError`, and the affected transaction is rolled back.	Database Problems	django	PostgreSQL Psycopg2 Django Transaction Deadlock Operational error Public Known Issue
CRE-2025-0073 High Impact: 9/10 Mitigation: 6/10	Redis Rejects Writes Due to Reaching 'maxmemory' Limit	The Redis instance has reached its configured 'maxmemory' limit. Because its active memory management policy does not permit the eviction of existing keys to free up space (as is the case when the 'noeviction' policy is in effect, which is often the default), Redis rejects new write commands by sending an "OOM command not allowed" error to the client.	Database Problems	redis-cli	Redis Redis CLI Memory Pressure Memory Data Loss Public
CRE-2025-0077 High Impact: 9/10 Mitigation: 7/10	PostgreSQL Fails to Extend File Due to Disk Full	PostgreSQL logs an error when it cannot extend a data file (table/index) because the filesystem is out of disk space. This prevents writes requiring new allocation.	Database Problems	postgresql	PostgreSQL Disk Full Write Failure Public
CRE-2025-0126 High Impact: 10/10 Mitigation: 7/10	MongoDB Replica Set Primary Election Failure	Detects high-severity MongoDB replica set primary election failures that result in no primary node being available, causing complete service unavailability. This rule targets catastrophic conditions that break replica set consensus: - Primary node failures followed by election timeouts where no secondary can become primary - Network partitions isolating replica set members and preventing quorum formation - Heartbeat failures and connectivity issues leading to election failures - Replica set state transitions indicating election problems	Database Problems	mongodb	High Availability Quorum Leader Election Network Timeout Crash Data Loss
CRE-2025-0130 High Impact: 9/10 Mitigation: 3/10	Supabase Self-Hosted: Postgres Container Fails to Start Due to Port Conflict	Detects when Supabase self-hosted Postgres container fails to start because another service is already using port 5432. This is a common issue during initial setup or when multiple Postgres instances are running on the same host. The failure prevents the entire Supabase stack from starting properly.	Database Problems	supabase	Supabase PostgreSQL Port Binding Configuration Startup Failure Self-Hosted Container Crash Public
CRE-2025-0132 Medium Impact: 8/10 Mitigation: 5/10	Supabase Self-Hosted: Database Connection Timeout and Service Failure	Detects when Supabase services lose connection to the PostgreSQL database due to timeouts, network issues, or database unavailability. This affects Auth, REST API, Storage, and all database-dependent operations. Occurs during database restarts, network partitions, or when database becomes unresponsive.	Database Problems	supabase	Supabase PostgreSQL Connection Timeout Network Self-Hosted Connectivity Public