CVE-2026-130082 · Package
NO FIX YET · SEE WHAT TO DO
django-tenants does not escape tenant schema names in its PostgreSQL backend, so the names are pasted straight into SQL statements. An attacker who can choose or influence a schema name can read other tenants' data or run SQL as the application's database user.
first public Oct 24, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications built on django-tenants 3.4.8 up to but not including 4.0.1 that use the PostgreSQL backend and let users influence tenant schema names are exposed. Apps with fixed tenant names, or that do not take schema names from requests, are much less exposed. unknown whether other backends are affected.
Not affected if fixed-schema-names, non-postgresql-backend
Who cares django, django-tenants, multi-tenant, postgresql
pip show django-tenants and see whether it is at least 4.0.1.4.0.1 or later (the range runs from 3.4.8 before 4.0.1).django-tenants 3.4.8 before 4.0.1 contains an SQL injection vulnerability in its PostgreSQL backend that allows attackers to inject SQL through unescaped tenant schema names. Attackers who can choose or influence a schema name can supply quote characters that are interpolated into SET search_path and CREATE, DROP or ALTER SCHEMA statements, letting them read other tenants' data or run SQL as the application's database user.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.