CVE-2023-46255: Password Leakage in github.com/authzed/spicedb
Summary
CVE-2023-46255: SpiceDB leaks information in log files when URI cannot be parsed. Affects github.com/authzed/spicedb versions < 1.27.0-rc1. Fixed in 1.27.0-rc1. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
github.com/authzed/spicedb is a Go package that provides a datastore for managing permissions in applications. It allows developers to define and enforce fine-grained access control policies. The package is widely used in various Go applications.
Vulnerability Detail
The vulnerability (CVE-2023-46255) in github.com/authzed/spicedb occurs when the provided datastore URI is malformed, such as when a password contains a colon (':'). In such cases, the full URI, including the password, is printed in the logs. This exposes the password in plaintext, which can lead to unauthorized access to the datastore. An attacker with access to the logs can potentially use the leaked password to gain unauthorized access to the database.
How To Fix
Latest published version: v1.57.0 as of 23 Oct 2026
go get github.com/authzed/spicedb@v1.57.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.27.0-rc1
This is the first release that contains the fix.
go get github.com/authzed/spicedb@v1.27.0-rc1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.
Conclusion
The vulnerability in github.com/authzed/spicedb exposes passwords in plaintext in the logs, potentially leading to unauthorized access to the datastore. Developers should upgrade to version 1.27.0 or later to fix this issue. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/authzed/spicedb →
FAQ
The vulnerability exposes passwords in plaintext in the logs, which can lead to unauthorized access to the datastore.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
Yes, the CVSS score for this vulnerability is 4.2.
There are no known exploits for this vulnerability at the moment.
No, removing the password from the URI will result in authentication failures and will not mitigate the risk. Upgrading to the fixed version is the recommended solution.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/authzed/spicedb.
