CVE-2026-130082 django-tenants 3.4.8 before 4.0.1 SQL Injection via Unescaped Schema Name
Attackers influencing a schema name can inject SQL via django-tenants' PostgreSQL backend to read or alter other tenants' data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- Yes
- Fix
- None listed
What is CVE-2026-130082?
CVE-2026-130082 is a high-severity SQL injection vulnerability in django-tenants, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-89
Which versions are affected by CVE-2026-130082?
1 open source package ship an affected version, including django-tenants.
An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.
| Package | Affected | Fixed in |
|---|---|---|
django-tenants PyPIpkg:pypi/django-tenants | From 3.4.8 | 4.0.1 |
How do I fix CVE-2026-130082?
Upgrade django-tenants to 4.0.1 or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-130082 being exploited?
There is no known exploitation of CVE-2026-130082 in the wild and no public exploit code.
Sources
Also known as GHSA-693j-7v9f-x7pw, GHSA-pg64-4qv2-75g5.