How severe is CVE-2025-58068?

No CVSS score has been assigned to CVE-2025-58068 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-58068?

CVE-2025-58068 affects the following packages: eventlet (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-58068?

Update eventlet to 0.40.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58068 is resolved across your whole dependency graph.

How do I detect CVE-2025-58068 in my PyPI dependencies?

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

How do I mitigate CVE-2025-58068 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.

Is CVE-2025-58068 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-58068 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-58068?

CVE-2025-58068 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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.

What type of vulnerability is CVE-2025-58068?

CVE-2025-58068 is classified as CWE-444 (CWE-444). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-58068 published, and has it been updated?

CVE-2025-58068 was published on August 29, 2025 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

CVE-2025-58068 — eventlet

Fix: eventlet/eventlet@0bfebd1

CVE-2025-58068 is a CWE-444 vulnerability in eventlet. A fix is available for eventlet — see the affected versions and patch details below.

Eventlet affected by HTTP request smuggling in unparsed trailers

Also known asGHSA-hw6f-rjfj-j7j7PYSEC-2026-1350

Published

Aug 29, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-2025-58068.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍eventlet

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

Impact

The Eventlet WSGI parser is vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer sections.

This vulnerability could enable attackers to:

Bypass front-end security controls
Launch targeted attacks against active site users
Poison web caches

Patches

Problem has been patched in eventlet 0.40.3.

The patch just drops trailers. If a backend behind eventlet.wsgi proxy requires trailers, then this patch BREAKS your setup.

Workarounds

Do not use eventlet.wsgi facing untrusted clients.

References

Patch https://github.com/eventlet/eventlet/pull/1062
This issue is similar to https://github.com/advisories/GHSA-9548-qrrj-x5pj

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

eventleteventlet

< 0.40.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eventlet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update eventlet to 0.40.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58068 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.

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 HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-58068 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenStack Services on OpenShift 18.0	`python-eventlet-0:0.33.1-7.el9ost`	RHSA-2026:1959
Red Hat OpenShift Container Platform 4.12	`openshift4/ose-ironic-agent-rhel9:1772155648`	RHSA-2026:3870
Red Hat OpenShift Container Platform 4.13	`openshift4/ose-ironic-agent-rhel9:1771853308`	RHSA-2026:3422
Red Hat OpenShift Container Platform 4.14	`openshift4/ose-ironic-agent-rhel9:1770733671`	RHSA-2026:2990
Red Hat OpenShift Container Platform 4.15	`openshift4/ose-ironic-agent-rhel9:1769530180`	RHSA-2026:1549
Red Hat OpenShift Container Platform 4.16	`openshift4/ose-ironic-agent-rhel9:1770654140`	RHSA-2026:2661
Red Hat OpenShift Container Platform 4.17	`openshift4/ose-ironic-agent-rhel9:1769561620`	RHSA-2026:1577
Red Hat OpenShift Container Platform 4.18	`openshift4/ose-ironic-agent-rhel9:1768710367`	RHSA-2026:1062

Frequently Asked Questions

### Impact The Eventlet WSGI parser is vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer sections. This vulnerability could enable attackers to: - Bypass front-end security controls - Launch targeted attacks against active site users - Poison web caches ### Patches Problem has been patched in eventlet 0.40.3. The patch just drops trailers. If a backend behind eventlet.wsgi proxy requires trailers, then this patch BREAKS your setup. ### Workarounds Do not use eventlet.wsgi facing untrusted clients. ### References - Patch https://github.com/eventlet/eventlet/pull

O3 Security · Impact-Aware SCA

Is CVE-2025-58068 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works