CVE-2012-5577 — keyring
HIGHCVE-2012-5577 is a high-severity (CVSS 7.5) Incorrect Default Permissions vulnerability in keyring. A fix is available for keyring — see the affected versions and patch details below.
Incorrect Default Permissions in keyring
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
keyringReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Python keyring lib before 0.10 created keyring files with world-readable permissions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | keyring | all versions | 0.10pip install --upgrade 'keyring==0.10' |
Affected Products
debian linuxdebiankeyringpythonDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keyring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keyring to 0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-5577 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2012-5577 in your dependencies?
Find it across PyPI, including transitive dependencies.