How severe is CVE-2023-41419?

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

Which packages are affected by CVE-2023-41419?

CVE-2023-41419 affects the following packages: gevent (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2023-41419?

Update gevent to 23.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41419 is resolved across your whole dependency graph.

How do I detect CVE-2023-41419 in my PyPI dependencies?

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

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

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 does O3 Security protect against CVE-2023-41419?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-41419 can be triaged on real exposure rather than presence alone.

Is CVE-2023-41419 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-41419, including 1 in-the-wild exploitation 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-2023-41419?

CVE-2023-41419 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2023-41419 published, and has it been updated?

CVE-2023-41419 was published on September 25, 2023 and was last updated on August 12, 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-2023-41419 — gevent

CRITICALFix: gevent/gevent@2f53c85

CVE-2023-41419 is a critical-severity (CVSS 9.8) vulnerability in gevent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for gevent — see the affected versions and patch details below.

Gevent allows remote attacker to escalate privileges

Also known asGHSA-x7m3-jprg-wc5gPYSEC-2023-177

Published

Sep 25, 2023

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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-2023-41419 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,166 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

1 pkg affected

🐍gevent

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 in Gevent before version 23.9.0 allows a remote attacker to escalate privileges via a crafted script to the WSGIServer component.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`gevent`	all versions	23.9.0`pip install --upgrade 'gevent==23.9.0'`

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 in Gevent before version 23.9.0 allows a remote attacker to esc…

github.comNVDSep 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gevent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gevent to 23.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41419 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-2023-41419 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2023-41419. 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.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`python-gevent-0:1.2.2-5.el8_10`	RHSA-2024:8834
Red Hat Enterprise Linux 8.2 Advanced Update Support	`python-gevent-0:1.2.2-5.el8_2`	RHSA-2024:7785
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	`python-gevent-0:1.2.2-5.el8_4`	RHSA-2024:8105
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	`python-gevent-0:1.2.2-5.el8_6`	RHSA-2024:7421
Red Hat Enterprise Linux 8.8 Extended Update Support	`python-gevent-0:1.2.2-5.el8_8`	RHSA-2024:8102
Red Hat OpenStack Platform 17.1 for RHEL 9	`python-gevent-0:21.1.2-2.el9ost`	RHSA-2023:7438

Frequently Asked Questions

An issue in Gevent before version 23.9.0 allows a remote attacker to escalate privileges via a crafted script to the WSGIServer component.

O3 Security · Impact-Aware SCA

Is CVE-2023-41419 in your dependencies?

O3 Security finds CVE-2023-41419 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works