CVE-2012-5577: Incorrect Default Permissions in keyring

keyring Updated 02 Oct 2025

Summary

11/03/2020
Yes i
High
7.5

CVE-2012-5577: Incorrect Default Permissions in keyring. Affects keyring versions < 0.10. Fixed in 0.10. How to fix ↓

Also tracked for

The same CVE-2012-5577 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The keyring library is a Python package available on PyPI. It provides a way to store and retrieve passwords and other sensitive information securely. The library creates keyring files to store this information. However, versions of the library before 0.10 had a vulnerability where these keyring files were created with world-readable permissions. This means that anyone with access to the file system could read the contents of the keyring files, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability (CVE-2012-5577) in the keyring library arises from the incorrect default permissions set on the keyring files. By creating these files with world-readable permissions, any user on the system can read the contents of the keyring files. This can lead to the exposure of sensitive information, such as passwords and other credentials, stored in the keyring. The impact of this vulnerability is high, as it allows unauthorized access to sensitive data.

How To Fix

Latest published version: 25.7.0 as of 22 Oct 2026

pip install --upgrade "keyring==25.7.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.10

This is the first release that contains the fix.

pip install --upgrade "keyring==0.10"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to a fixed version of the keyring library.

Conclusion

The keyring library before version 0.10 had a vulnerability that allowed unauthorized access to sensitive information stored in keyring files. To fix this vulnerability, it is recommended to upgrade to version 0.10 or later of the keyring library. For more information and support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for keyring →

Share this vulnerability

FAQ

The keyring library is a Python package that provides a secure way to store and retrieve passwords and other sensitive information.

The vulnerability allows unauthorized access to sensitive information stored in the keyring, such as passwords and credentials.

To fix this vulnerability, upgrade to version 0.10 or later of the keyring library.

There are no specific workarounds mentioned for this vulnerability. Upgrading to a fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for keyring.

How To Fix

Latest published version: 25.7.0 as of 22 Oct 2026

pip install --upgrade "keyring==25.7.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.10

This is the first release that contains the fix.

pip install --upgrade "keyring==0.10"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback