CVE-2022-34265

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 73.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS: 73%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
—
EPSS
99.4%
KEV
Not listed

Published

July 4, 2022

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Jun 9, 2026
No patch confirmed yet.
generic

[SECURITY] Fedora 37 Update: python-django-4.0.10-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HWY6DQWRVBALV73BPUVBXC3QIYUM24IK/
generic

Redirecting to Google Groups

https://groups.google.com/forum/#%21forum/django-announce
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/4.0/releases/security/
generic

Django security releases issued: 4.0.6 and 3.2.14 | Weblog | Django

https://www.djangoproject.com/weblog/2022/jul/04/security-releases/
generic

[SECURITY] [DSA 5254-1] python-django security update

https://www.debian.org/security/2022/dsa-5254
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20220818-0006/
generic

[SECURITY] Fedora 38 Update: python-django-4.0.10-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LTZVAKU5ALQWOKFTPISE257VCVIYGFQI/

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-django-doc (2:3.2.12-2ubuntu1.1) @ jammy2026-05-25ubuntu
redhatpython-django-0:3.2.14-2.el8pc2022-11-16redhat
redhatpython-django-0:3.2.14-3.el8ui2022-07-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django3.2 ... 4.0.5 (20 versions)4.0.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:59 UTCEG score recompute
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-17 04:24 UTCOSV refresh
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-13 22:28 UTCEPSS rescore
  15. 2026-07-13 22:28 UTCEPSS rescore
  16. 2026-07-13 06:11 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-11 08:25 UTCEPSS rescore
  19. 2026-07-06 02:21 UTCEPSS rescore
  20. 2026-07-06 02:21 UTCEPSS rescore
  21. 2026-07-04 06:29 UTCEPSS rescore
  22. 2026-07-04 06:29 UTCEPSS rescore
  23. 2026-07-01 15:04 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
Show 30 more
  1. 2026-06-29 02:32 UTCOSV refresh
  2. 2026-06-28 14:06 UTCEPSS rescore
  3. 2026-06-28 04:54 UTCEPSS rescore
  4. 2026-06-28 04:54 UTCEPSS rescore
  5. 2026-06-25 13:48 UTCEPSS rescore
  6. 2026-06-25 13:48 UTCEPSS rescore
  7. 2026-06-24 14:03 UTCEPSS rescore
  8. 2026-06-24 14:03 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-23 21:31 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-18 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-17 17:51 UTCEPSS rescore
  15. 2026-06-16 17:51 UTCEPSS rescore
  16. 2026-06-15 17:46 UTCEPSS rescore
  17. 2026-06-14 23:15 UTCEPSS rescore
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-12 23:10 UTCEPSS rescore
  20. 2026-06-11 22:25 UTCOSV refresh
  21. 2026-06-08 14:15 UTCEPSS rescore
  22. 2026-06-08 14:15 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-06-05 22:45 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-31 00:15 UTCEPSS rescore
  27. 2026-05-29 13:43 UTCEPSS rescore
  28. 2026-05-29 13:43 UTCEPSS rescore
  29. 2026-05-25 19:28 UTCEG score recompute
  30. 2026-05-25 19:28 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCZhaoQi99/CVE-2022-34265
    First seen Aug 24, 2022

    PoC for CVE-2022-34265

    Open source ↗
  • GitHub PoCtraumatising/CVE-2022-34265
    First seen Jul 13, 2022

    CVE-2022-34265 Vulnerability

    Open source ↗
  • GitHub PoCaeyesec/CVE-2022-34265
    First seen Jul 7, 2022

    PoC for CVE-2022-34265 (Django)

    Open source ↗

Frequently asked(5)

What is CVE-2022-34265?
CVE-2022-34265 is a critical vulnerability published on July 4, 2022. An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
When was CVE-2022-34265 disclosed?
CVE-2022-34265 was first published in the National Vulnerability Database on July 4, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-34265 actively exploited?
CVE-2022-34265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-34265?
CVE-2022-34265 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-34265?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-34265, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-34265

Explore →

Is Your Infrastructure Affected by CVE-2022-34265?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs