For your digest
zope2: Moderate severity vulnerability that affects Zope2
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
zope2 (PyPI)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- zope2 (PyPI): from 2.8.0, before 2.8.12
- zope2 (PyPI): from 2.9.0, before 2.9.12
- zope2 (PyPI): from 2.10.0, before 2.10.11
- zope2 (PyPI): from 2.11.0, before 2.11.6
- zope2 (PyPI): from 2.12.0, before 2.12.3
- zope2 (PyPI): from 2.8.0, before 2.8.12; from 2.9.0, before 2.9.12; from 2.10.0, before 2.10.11; from 2.11.0, before 2.11.6; from 2.12.0, before 2.12.3
The fix
zope2 (PyPI) fixed in 2.8.12
pippython -m pip install zope2==2.8.12uvuv add zope2==2.8.12poetrypoetry add zope2@2.8.12Check what is installedpython -m pip show zope2Paste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope2 to 2.8.12 or the nearest later release, to fix CVE-2010-1104. 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.zope2 (PyPI) fixed in 2.9.12
pippython -m pip install zope2==2.9.12uvuv add zope2==2.9.12poetrypoetry add zope2@2.9.12Check what is installedpython -m pip show zope2Paste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope2 to 2.9.12 or the nearest later release, to fix CVE-2010-1104. 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.zope2 (PyPI) fixed in 2.10.11
pippython -m pip install zope2==2.10.11uvuv add zope2==2.10.11poetrypoetry add zope2@2.10.11Check what is installedpython -m pip show zope2Paste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope2 to 2.10.11 or the nearest later release, to fix CVE-2010-1104. 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.zope2 (PyPI) fixed in 2.11.6
pippython -m pip install zope2==2.11.6uvuv add zope2==2.11.6poetrypoetry add zope2@2.11.6Check what is installedpython -m pip show zope2Paste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope2 to 2.11.6 or the nearest later release, to fix CVE-2010-1104. 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.zope2 (PyPI) fixed in 2.12.3
pippython -m pip install zope2==2.12.3uvuv add zope2==2.12.3poetrypoetry add zope2@2.12.3Check what is installedpython -m pip show zope2Paste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope2 to 2.12.3 or the nearest later release, to fix CVE-2010-1104. 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
- First published here, as "For your digest".