Advisories
For your digest

pyesasky: The pyesasky for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party. The current versio…

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

Does it affect what I run?

pyesasky (PyPI)

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

Who is affected

  • pyesasky (PyPI): from 1.2.0, before 1.4.3

The fix

  • pyesasky (PyPI) fixed in 1.4.3

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