Race condition in zenml

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:L

EPSS

• CVE-2024-2032: 0.29% estimated exploitation activity in the next 30 days; percentile 21.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A race condition vulnerability exists in zenml-io/zenml versions up to and including 0.55.3, which allows for the creation of multiple users with the same username when requests are sent in parallel. This issue was fixed in version 0.55.5. The vulnerability arises due to insufficient handling of concurrent user creation requests, leading to data inconsistencies and potential authentication problems. Specifically, concurrent processes may overwrite or corrupt user data, complicating user identification and posing security risks. This issue is particularly concerning for APIs that rely on usernames as input parameters, such as PUT /api/v1/users/testrace, where it could lead to further complications.

Published by the source

6 Jun 2024, 21:30 UTC

Last modified by the source

14 Oct 2024, 18:53 UTC

Source last checked

26 Oct 2026, 13:21 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-c546-8jmq-hprj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-c546-8jmq-hprj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-2032

Advisory: Race condition in zenml
IDs: CVE-2024-2032, GHSA-c546-8jmq-hprj
Record: https://patchnext.com/advisories/cve-2024-2032 (revision 2, source checked 26 Oct 2026, 13:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zenml 0.55.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI zenml: affected < 0.55.5; fixed in 0.55.5

## Suggested inspection (read-only)
- `python -m pip show zenml`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zenml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c546-8jmq-hprj (OSV record GHSA-c546-8jmq-hprj lists affected ranges: PyPI zenml >=0 <0.55.5 (fixed))
- Verified: https://github.com/advisories/GHSA-c546-8jmq-hprj (GitHub-reviewed advisory GHSA-c546-8jmq-hprj lists affected ranges: PyPI zenml >=0 <0.55.5)

Commands are suggestions: review each one before running it.