Advisories
For your digest

pyyaml: Deserialization of Untrusted Data in PyYAML

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

pyyaml (PyPI)

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

Who is affected

  • pyyaml (PyPI): from 5.1, before 5.2
  • pyyaml (PyPI): from 5.1, before 5.2b1

The fix

  • pyyaml (PyPI) fixed in 5.2

    pip
    python -m pip install pyyaml==5.2
    uv
    uv add pyyaml==5.2
    poetry
    poetry add pyyaml@5.2
    Check what is installed
    python -m pip show pyyaml
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency pyyaml to 5.2 or the nearest later release, to fix CVE-2019-20477. 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.
  • pyyaml (PyPI) fixed in 5.2b1

    pip
    python -m pip install pyyaml==5.2b1
    uv
    uv add pyyaml==5.2b1
    poetry
    poetry add pyyaml@5.2b1
    Check what is installed
    python -m pip show pyyaml
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency pyyaml to 5.2b1 or the nearest later release, to fix CVE-2019-20477. 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

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".
  2. Fixed releases changed: added pyyaml 5.2b1.