Advisories
This weekExploitable · Confirmed

parso: Deserialization vulnerability exists in parso

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

parso (PyPI)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • parso (PyPI): every version, before 0.5.0

The fix

  • parso (PyPI) fixed in 0.5.0

    pip
    python -m pip install parso==0.5.0
    uv
    uv add parso==0.5.0
    poetry
    poetry add parso@0.5.0
    Check what is installed
    python -m pip show parso
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency parso to 0.5.0 or the nearest later release, to fix CVE-2019-12760. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "Listed".
  2. Level changed from "Listed" to "For your digest".
  3. Fixed releases changed: added parso 0.5.0.
  4. Level changed from "For your digest" to "This week".
  5. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))