CVE-2026-130082

validatedZero produced an exploit or a check.

GHSA-pg64-4qv2-75g5 ↗EUVD-2026-126711 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
django-tenants >= 3.4.8, < 4.0.1
fixed in 4.0.1
ETK-2026-4633Zero's internal tracking ID, independent of the CVE number., permanent identifier
+3h16mTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+3h16magent stopped
0
+1h
+2h
+3h

description

django-tenants versions 3.4.8 through releases before 4.0.1 mishandle tenant schema names in the PostgreSQL backend. An attacker who can control or influence a schema name may trigger unintended database commands, potentially accessing data from other tenants or operating with the application's database privileges.

mitigation

Upgrade django-tenants to version 4.0.1 or later. Until upgraded, prevent untrusted users from supplying or altering tenant schema names and restrict the application's database account to the minimum required permissions.

fixed in 4.0.1

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.30%23rd percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-16 21:59Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-16 21:59Z
    ghsa: trigger signal, started the run
  2. 2026-11-16 21:59Z

this entry in the feed

GET /api/v1/feed/CVE-2026-130082

{
  "etk_id": "ETK-2026-4633",
  "cve_id": "CVE-2026-130082",
  "display_id": "CVE-2026-130082",
  "ghsa_id": "GHSA-pg64-4qv2-75g5",
  "euvd_id": "EUVD-2026-126711",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection through tenant schema names in django-tenants",
  "summary": "django-tenants versions 3.4.8 through releases before 4.0.1 mishandle tenant schema names in the PostgreSQL backend. An attacker who can control or influence a schema name may trigger unintended database commands, potentially accessing data from other tenants or operating with the application's database privileges.",
  "mitigation": "Upgrade django-tenants to version 4.0.1 or later. Until upgraded, prevent untrusted users from supplying or altering tenant schema names and restrict the application's database account to the minimum required permissions.",
  "vendor": "django-tenants",
  "product": "django-tenants",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.4.8, < 4.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.0.1"
      ],
      "package_name": "django-tenants",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2333,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 10.981824333333334,
  "t0_at": "2026-11-16T21:59:57.176000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-17T01:15:55.659809+00:00",
      "days": 0.13609356260416666,
      "is_lower_bound": false,
      "measured_at": "2026-11-16T21:59:57.176000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-16T21:59:57.176000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-16T21:59:57.176000+00:00",
      "url": "https://github.com/advisories/GHSA-pg64-4qv2-75g5"
    }
  }
}

published 2026-11-17 01:04Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.