On this page (7 sections)

Ubuntu has published USN-9083-1, a security notice for the gevent Python networking library. The notice says the gevent WSGI server incorrectly validated chunked transfer encoding trailers in HTTP requests, which a remote attacker could possibly use for HTTP request smuggling, leading to privilege escalation. The notice references CVE-2023-41419.

If you run a Python web application on Ubuntu 16.04, 18.04, 20.04 or 22.04 LTS and serve it with gevent's built-in WSGI server, this is worth checking today. The fixed packages are delivered through Ubuntu Pro (ESM Apps), so the update path depends on whether your machines are enrolled.

What happened

Ubuntu's notice describes a single issue: the gevent WSGI server did not correctly validate trailers sent with chunked transfer encoding. Trailers are optional header-like fields that can follow the body of a chunked HTTP request. The notice summarizes the impact as unintended access to network services and says an attacker could possibly use the flaw for request smuggling.

The research for this story is one Ubuntu notice. It gives no CVSS score, no report of active exploitation and no technical write-up, so details such as exact trigger conditions are not confirmed here. See the CVE record for CVE-2023-41419 for anything beyond what Ubuntu states.

Why request smuggling matters

HTTP request smuggling happens when two systems in a chain, for example a reverse proxy and an application server, disagree about where one request ends and the next begins. An attacker can exploit that disagreement to slip a request past front-end checks, so the back end treats it as legitimate. Typical consequences are bypassed access controls, poisoned caches or requests attributed to other users.

Ubuntu's wording, "privilege escalation", fits that pattern: if a proxy or firewall in front of gevent enforces rules, a smuggled request may reach the application without those rules applying. How realistic that is for your site depends on your setup, which the notice does not describe.

Who is affected

The notice lists the following packages and fixed versions. All fixes are marked as available through Ubuntu Pro via ESM Apps, with a note that a community fix might become publicly available in the future.

Fixed package versions from USN-9083-1
Ubuntu releasePackageFixed version
22.04 LTS (jammy)python3-gevent21.8.0-1ubuntu0.1~esm1
20.04 LTS (focal)python3-gevent1.4.0-1.2ubuntu0.1~esm1
18.04 LTS (bionic)python-gevent, python3-gevent1.2.2-2ubuntu0.1~esm1
16.04 LTS (xenial)python-gevent, python3-gevent1.1.0-2ubuntu0.1~esm1

The flaw is described as being in the gevent WSGI server. Applications that use gevent only for coroutines or outbound networking, and serve HTTP through something else, are not described as affected by the notice. Applications that use gevent's WSGI server directly, or through a framework runner that wraps it, are the ones to review first.

How to check your exposure

First find out whether gevent is installed from Ubuntu packages. This read-only command lists installed gevent packages and their versions on Debian-based systems such as Ubuntu. Compare the version column with the fixed versions in the table above.

List installed gevent packages and versions (Ubuntu)Shell
dpkg -l | grep -i gevent

If your application runs in a virtualenv or container, the system package may not be the copy in use. This read-only command shows the version of gevent that a given Python interpreter would import. Run it with the interpreter your application uses.

Show the gevent version a Python 3 interpreter importsShell
python3 -c "import gevent; print(gevent.__version__)"
The Ubuntu notice only covers Ubuntu-packaged gevent. A copy installed with pip in a virtualenv or container is not updated by the Ubuntu fix, and the research does not state which upstream gevent release contains the fix. Consult the CVE record for CVE-2023-41419 for that information.

What to do now

  1. Run the dpkg check above on each Ubuntu server and note any python-gevent or python3-gevent packages below the fixed versions.
  2. Identify which applications use the gevent WSGI server directly, and whether a reverse proxy or load balancer sits in front of them.
  3. If your machines are enrolled in Ubuntu Pro with ESM Apps, apply a standard system update, as the notice advises, then re-run the version check.
  4. If you are not enrolled, decide whether to enable Ubuntu Pro (the notice says it is free for up to five machines) or to move the app to another WSGI server.
  5. Restart the application services that import gevent so they load the updated library.
  6. For pip or container installs, check the CVE record for CVE-2023-41419 to find a fixed upstream release, since the research does not name one, and update the bundled copy accordingly.

On a system with Ubuntu Pro attached, a standard update is the documented route. These are the usual commands for refreshing package lists and upgrading only the gevent package.

Caution. Restarting an application service interrupts active requests. Schedule the restart in a maintenance window or drain traffic first.
Update only the gevent package (Ubuntu with Ubuntu Pro ESM Apps enabled)Shell
sudo apt update
sudo apt install --only-upgrade python3-gevent

On 18.04 and 16.04, python-gevent for Python 2 is also listed, so upgrade that package name too if it is installed.

Detection and monitoring

Request smuggling attempts are hard to spot from the outside, and the research gives no indicators of compromise. Practical steps are to review reverse proxy and application logs for requests with unusual chunked bodies or trailer fields, and for mismatches where the proxy logs one request but the application logs two. Treat that as a hunting hint, not a confirmed signature for this flaw.

Keeping a front-end layer that normalizes or rejects ambiguous requests reduces the room for desynchronization in general; see what a WAF does for background. For ongoing visibility into certificate, DNS and header changes on your sites, Webforta Monitor can help, though it does not patch or specifically detect this library flaw.

Timeline

  • 12 November 2026: Ubuntu publishes USN-9083-1 for gevent, referencing CVE-2023-41419.

No other dates, such as when the issue was first reported or fixed upstream, are given in the research.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9083-1: gevent vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • gevent
  • Ubuntu
  • HTTP request smuggling
  • Python
  • USN