ai-flow Deserialization of Untrusted Data vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2024-0960: 0.72% estimated exploitation activity in the next 30 days; percentile 53.92 (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 vulnerability was found in flink-extended ai-flow 0.3.1. It has been declared as critical. Affected by this vulnerability is the function cloudpickle.loads of the file \aiflow\cli\commands\workflowcommand.py. The manipulation leads to deserialization. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-252205 was assigned to this vulnerability.

Published by the source

27 Jan 2024, 12:30 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7mgg-3rq2-hff4

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7mgg-3rq2-hff4

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

# Patch Next advisory brief: CVE-2024-0960

Advisory: ai-flow Deserialization of Untrusted Data vulnerability
IDs: CVE-2024-0960, GHSA-7mgg-3rq2-hff4
Record: https://patchnext.com/advisories/cve-2024-0960 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI ai-flow: affected <= 0.3.1

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ai-flow.
- 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-7mgg-3rq2-hff4 (OSV record GHSA-7mgg-3rq2-hff4 lists affected ranges: PyPI ai-flow >=0 <=0.3.1)
- Verified: https://github.com/advisories/GHSA-7mgg-3rq2-hff4 (GitHub-reviewed advisory GHSA-7mgg-3rq2-hff4 lists affected ranges: PyPI ai-flow >=0 <=0.3.1)

Commands are suggestions: review each one before running it.