CVE-2026-130082 json
django-tenants 3.4.8 before 4.0.1 SQL Injection via Unescaped Schema Name
published 25d ago modified 21h ago also EUVD-2026-126711 , GHSA-693j-7v9f-x7pw
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository django-tenants/django-tenants. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
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.
Patch / fix
- django-tenants django-tenants 4.0.1
Is CVE-2026-130082 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 21h ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 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/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 |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | django-tenants | django-tenants/django-tenants | >= 3.4.8, < 4.0.1 |
Affected products
- django-tenants django-tenants
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/django-tenants/django-tenants/commit/46d89c0fccc820f88657e6ec152ba855072571ff
patch
-
github.com
/django-tenants/django-tenants/security/advisories/GHSA-693j-7v9f-x7pw
vendor-advisory, advisory
-
github.com
/django-tenants/django-tenants/releases/tag/v4.0.1
release-notes
-
github.com
/django-tenants/django-tenants/blob/v4.0.0/django_tenants/postgresql_backend/base.py#L208-L213
technical-description
-
github.com
/django-tenants/django-tenants/blob/v4.0.0/django_tenants/postgresql_backend/base.py#L46
technical-description
-
vulncheck.com
/advisories/django-tenants-3.4.8-before-4.0.1-sql-injection-via-unescaped-schema-name
third-party-advisory
Sources
- CVE List CVE-2026-130082
- NVD CVE-2026-130082
- Maintainer advisory GHSA-693j-7v9f-x7pw
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of django-tenants/django-tenants published their own advisory on GitHub. Reviewed sources take precedence over it.