CVE-2024-34069 is a high-severity (CVSS 7.5) Cross-Site Request Forgery (CSRF) vulnerability in werkzeug. A fix is available for werkzeug — see the affected versions and patch details below.
Werkzeug's improper usage of a pathname and improper CSRF protection results in the remote command execution
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-34069.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-34069 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
werkzeugReal-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
Werkzeug is a comprehensive WSGI web application library. The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger. This vulnerability is fixed in 3.0.3.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | werkzeug | all versions | 3.0.3pip install --upgrade 'werkzeug==3.0.3' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for werkzeug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update werkzeug to 3.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-34069 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-34069 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-34069. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
Werkzeug's debugger allows an attacker to potentially execute code on a developer's machine. This can occur if the attacker tricks the developer into interacting with a controlled domain and subdomain and entering the debugger PIN. Although the debugger is meant to run locally, successful exploitation can give the…
| Product | Fixed in | Advisory |
|---|---|---|
| Ironic content for Red Hat OpenShift Container Platform 4.12 | python-werkzeug-0:2.0.3-6.el9 | RHSA-2024:5810 |
| Red Hat Ceph Storage 7.1 | ceph-2:18.2.1-329.el8cp | RHSA-2025:4664 |
| Red Hat Ceph Storage 7.1 | rhceph/rhceph-7-rhel9:7-529 | RHSA-2025:9340 |
| Red Hat OpenShift Container Platform 4.14 | openshift4/cloud-network-config-controller-rhel8:v4.14.0-202408260910.p0.g1bd0464.assembly.stream.el8 | RHSA-2024:6406 |
| Red Hat OpenShift Container Platform 4.15 | python-werkzeug-0:2.2.3-3.el9 | RHSA-2024:6016 |
| Red Hat OpenShift Container Platform 4.16 | openshift4/ose-ironic-rhel9:v4.16.0-202408051209.p0.ga428def.assembly.stream.el9 | RHSA-2024:5107 |
| Red Hat OpenStack Platform 16.2 | python-werkzeug-0:0.14.1-13.el8ost | RHSA-2024:10696 |
| Red Hat OpenStack Platform 17.1 for RHEL 8 | python-werkzeug-0:2.0.1-9.el8ost | RHSA-2024:9975 |
Frequently Asked Questions
Is CVE-2024-34069 in your dependencies?
O3 Security finds CVE-2024-34069 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.