Skip to main content
VulnerabilityPublished

CVE-2026-130082: django-tenants · SQL Injection

Affects django-tenantsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.1 soon.

Data as of 16 Nov 2026, 22:20 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 4.0.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade django-tenants to 4.0.1.

Affected software

ProductAffectedFixed in
django-tenantsdjango-tenantsAffected
  • >=3.4.8 <4.0.1
Fixed in
  • 4.0.1
PyPIdjango-tenantspkg:pypi/django-tenantsOther threatsAffected
  • >=3.4.8 <4.0.1
Fixed in
  • 4.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade django-tenants to version 4.0.1 or later, where this SQL injection vulnerability is fixed. No other mitigations are specified or recommended by the vendor.

Description

django-tenants versions 3.4.8 up to but not including 4.0.1 contain an SQL injection vulnerability in the PostgreSQL backend. This flaw allows attackers who can influence tenant schema names to inject malicious SQL via unescaped schema identifiers. Exploitation can lead to unauthorized reading of other tenants' data or execution of arbitrary SQL commands as the application's database user. The vulnerability is fixed in version 4.0.1.

References

Community reviews

Loading reviews…