How severe is CVE-2022-34265?

CVE-2022-34265 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-34265?

CVE-2022-34265 affects the following packages: django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-34265?

Update django to 3.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34265 is resolved across your whole dependency graph.

How do I detect CVE-2022-34265 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-34265 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2022-34265 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2022-34265, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-34265?

CVE-2022-34265 has an EPSS (Exploit Prediction Scoring System) score of 73.6%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2022-34265?

CVE-2022-34265 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-34265 published, and has it been updated?

CVE-2022-34265 was published on July 4, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2022-34265 — django

CRITICALFix: django/django@0dc9c01

CVE-2022-34265 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. 7 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection

Also known asBIT-django-2022-34265GHSA-p64x-8rxx-wf6qPYSEC-2022-213

Published

Jul 4, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

7 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

73.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 3.2a1&&< 3.2.14	3.2.14`pip install --upgrade 'django==3.2.14'`
🐍PyPI	`django`	≥ 4.0a1&&< 4.0.6	4.0.6`pip install --upgrade 'django==4.0.6'`

Affected Products

1 product · 2 configurations

Application

djangodjangoproject

≥ 4.0 && < 4.0.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6…

github.comGithubJul 2022

Report on github.com

github.comGithubJul 2022

Report on github.com

github.comGithubJul 2022

Report on github.com

github.comGithubAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 3.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34265 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Applications that constrain the lookup name and kind choice to a known safe list are unaffected. Red Hat Satellite 6 versions include affected versions of python-django, however, the product is not vulnerable since it does not make use of vulnerable functions. Future updates may fix this issue.

Product	Fixed in	Advisory
Red Hat Satellite 6.12 for RHEL 8	`python-django-0:3.2.14-2.el8pc`	RHSA-2022:8506
RHUI 4 for RHEL 8	`python-django-0:3.2.14-3.el8ui`	RHSA-2022:5738

UbuntuCRITICAL

USN-5501-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-34265 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2022-34265 — django

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-34265 in your dependencies?