SpiceDB's SPICEDB_DATASTORE_CONN_URI is leaked on startup logsGHSA-jf4f-rr2c-9m58
MEDIUMGHSA-jf4f-rr2c-9m58 is a medium-severity (CVSS 6) CWE-532 vulnerability in github.com/authzed/spicedb. A fix is available for github.com/authzed/spicedb — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jf4f-rr2c-9m58.
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
github.com/authzed/spicedbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
SpiceDB is an open source database system for creating and managing security-critical application permissions. In versions 1.49.0 through 1.51.0, when SpiceDB starts with log level info, the startup "configuration" log will include the full datastore DSN, including the plaintext password, inside DatastoreConfig.URI. This issue has been fixed in version 1.51.1. If users are unable to immediately upgrade, they can work around this issue by changing the log level to warn or error.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/authzed/spicedb | ≥ 1.49.0&&< 1.51.1 | 1.51.1go get github.com/authzed/spicedb@v1.51.1 |
Affected Products
spicedbauthzedDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/authzed/spicedb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/authzed/spicedb to 1.51.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jf4f-rr2c-9m58 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
To exploit this vulnerability, a local attacker needs to have read access to the startup configuration log. Due to this reason, this flaw has been rated with a moderate severity.
To mitigate this flaw, configure the log level to 'warn' or 'error', instead of 'info'.Source: Red Hat security advisory for GHSA-jf4f-rr2c-9m58 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-jf4f-rr2c-9m58 in your dependencies?
Find it across Go, including transitive dependencies.