Security release
This release fixes a SQL injection vulnerability caused by unescaped tenant
schema names in generated SQL (SET search_path, CREATE SCHEMA,
DROP SCHEMA, ALTER SCHEMA ... RENAME). Applications that let an untrusted
user influence a tenant's schema_name could be exploited for cross-tenant
data access or arbitrary SQL execution.
Affected: 3.4.8 – 4.0.0. All users should upgrade.
See the advisory for full details, impact and mitigations:
GHSA-693j-7v9f-x7pw
Upgrade note
Schema names may no longer contain ", ', \, ;, line breaks or NUL. Such
names are extremely unusual; a tenant using one will raise ValidationError
after upgrading. Letters, digits, underscores, hyphens and mixed case are still
accepted.