Skip to main content

Tag: Psycopg2

Python client errors related to connecting or querying PostgreSQL using psycopg2.

IDTitleDescriptionCategoryTechnologyTags
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 ProblemsdjangoSslPsycopg2ForkThreadsDjangoInstrumentationOpentelemetryKnown IssuePublic
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 ProblemsdjangoPostgreSQLPsycopg2DjangoTransactionDeadlockOperational errorPublicKnown Issue