Credential disclosure via unredacted datastore URI logging
Published Apr 14, 2026 · Updated Apr 15, 2026
Sensitive-data exposure in AuthZed SpiceDB 1.49.0 through 1.51.0 allows local users to read datastore credentials from startup logs. At info level, the startup configuration logger serializes DatastoreConfig.URI in full instead of redacting the password embedded in the datastore DSN. Exposure requires access to SpiceDB startup logs and an info-level launch; it discloses the datastore password without altering data or service availability.
Summary
What happened
Sensitive-data exposure in AuthZed SpiceDB 1.49.0 through 1.51.0 allows local users to read datastore credentials from startup logs. At info level, the startup configuration logger serializes DatastoreConfig.URI in full instead of redacting the password embedded in the datastore DSN. Exposure requires access to SpiceDB startup logs and an info-level launch; it discloses the datastore password without altering data or service availability.
The record
- CVE
- CVE-2026-40091
- Published
- Apr 14, 2026
- Updated
- Apr 15, 2026
- Vendor
- AuthZed
- Product
- SpiceDB
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.49.0, < 1.51.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo