Skip to main content
Menu
CVEs

CVE

django-tenants SQL injection via unescaped schema names in PostgreSQL

Affects django-tenants 3.4.8 through 4.0.0 where an untrusted user can set or influence a tenant's schema_name without sanitisation. Fixed in 4.0.1.

CVE-2026-130082

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected versions are 3.4.8 through 4.0.0 (fixed in 4.0.1). The application must allow an untrusted user to set or influence a tenant's schema_name without applying its own sanitisation. Not affected when only trusted administrators create tenants, or when the application generates or slugifies schema names.

Published
Last modified
Reference
Last checked
27/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Who should check

Teams running django-tenants 3.4.8 through 4.0.0 on PostgreSQL where untrusted users can choose or influence tenant schema names, such as sign-up flows deriving schema names from subdomains or organisation names.

“Affected: >= 3.4.8, <= 4.0.0”

github.com

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects PyPI packages
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affected versions are 3.4.8 through 4.0.0 (fixed in 4.0.1). The application must allow an untrusted user to set or influence a tenant's schema_name without applying its own sanitisation. Not affected when only trusted administrators create tenants, or when the application generates or slugifies schema names.
  • Upgrade to a fixed version: 4.0.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130082 (django-tenants 3.4.8 before 4.0.1 SQL Injection via Unescaped Schema Name), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130082 (entry last updated 2026-11-16):
Affected:
- PyPI package django-tenants: from 3.4.8, fixed in 4.0.1
Fixed versions: 4.0.1.
Conditions (all must be true for the bug to be hit):
- Affected versions are 3.4.8 through 4.0.0 (fixed in 4.0.1). (source: https://github.com/django-tenants/django-tenants/security/advisories/GHSA-693j-7v9f-x7pw)
- The application must allow an untrusted user to set or influence a tenant's schema_name without applying its own sanitisation. (source: https://github.com/django-tenants/django-tenants/security/advisories/GHSA-693j-7v9f-x7pw)
- Not affected when only trusted administrators create tenants, or when the application generates or slugifies schema names. (source: https://github.com/django-tenants/django-tenants/security/advisories/GHSA-693j-7v9f-x7pw)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130082 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130082 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/django-tenants/django-tenants/security/advisories/GHSA-693j-7v9f-x7pw
- https://github.com/django-tenants/django-tenants/commit/46d89c0fccc820f88657e6ec152ba855072571ff
- https://github.com/django-tenants/django-tenants/releases/tag/v4.0.1
- https://github.com/django-tenants/django-tenants/blob/v4.0.0/django_tenants/postgresql_backend/base.py#L208-L213
- https://github.com/django-tenants/django-tenants/blob/v4.0.0/django_tenants/postgresql_backend/base.py#L46
- https://www.vulncheck.com/advisories/django-tenants-3.4.8-before-4.0.1-sql-injection-via-unescaped-schema-name
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130082
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130082"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130082

Is CVE-2026-130082 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

When an untrusted user can set or influence a tenant's schema_name without sanitisation, SQL injection becomes possible. This can let them read other tenants' data or run SQL as the application's database user. For a superuser role, it can also lead to command execution on the database host.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-130082?

django-tenants (PyPI): from 3.4.8 before 4.0.1.Source: cve.now feed data

Am I affected, and how do I check?

Versions 3.4.8 through 4.0.0 are affected. The bug needs an application that lets untrusted users set or influence a tenant's schema_name without its own sanitisation. Deployments where only trusted administrators create tenants, or where the application generates or slugifies schema names, are not affected. To check, look at the installed django-tenants version and how tenant schema names are set when tenants are created.Source: github.com, vulncheck.com

How do I fix CVE-2026-130082?

Upgrade django-tenants to 4.0.1, which is the fixed version.Source: github.com, vulncheck.com