# 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.

- **Severity:** High 8.7 (`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`)
- **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 available:** No
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-693j-7v9f-x7pw, GHSA-pg64-4qv2-75g5

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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 | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `django-tenants` | PyPI | `pkg: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.

## Is CVE-2026-130082 being exploited?

There is no known exploitation of CVE-2026-130082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130082 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-130082 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.

Affected packages and fixed versions:
- django-tenants (PyPI): affected from 3.4.8; fixed in 4.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130082/ (Markdown: https://insights.sbomify.com/CVE-2026-130082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130082
- OSV: https://osv.dev/vulnerability/CVE-2026-130082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130082/
Summaries are generated and may contain mistakes; the official description above is the record.
