Missing ratelimit on passwrod resets in zenml

Exploitation

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

CVSS

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

EPSS

• CVE-2024-4311: 0.51% estimated exploitation activity in the next 30 days; percentile 43.46 (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.

zenml-io/zenml version 0.56.4 is vulnerable to an account takeover due to the lack of rate-limiting in the password change function. An attacker can brute-force the current password in the 'Update Password' function, allowing them to take over the user's account. This vulnerability is due to the absence of rate-limiting on the '/api/v1/current-user' endpoint, which does not restrict the number of attempts an attacker can make to guess the current password. Successful exploitation results in the attacker being able to change the password and take control of the account.

Published by the source

14 Nov 2024, 18:30 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j3vq-pmp5-r5xj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j3vq-pmp5-r5xj

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

# Patch Next advisory brief: CVE-2024-4311

Advisory: Missing ratelimit on passwrod resets in zenml
IDs: CVE-2024-4311, GHSA-j3vq-pmp5-r5xj
Record: https://patchnext.com/advisories/cve-2024-4311 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zenml 0.57.0rc2. A vendor fix does not mean a deployment is fixed.

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

## 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-j3vq-pmp5-r5xj (OSV record GHSA-j3vq-pmp5-r5xj lists affected ranges: PyPI zenml >=0 <0.57.0rc2 (fixed))
- Verified: https://github.com/advisories/GHSA-j3vq-pmp5-r5xj (GitHub-reviewed advisory GHSA-j3vq-pmp5-r5xj lists affected ranges: PyPI zenml >=0 <0.57.0rc2)

Commands are suggestions: review each one before running it.