CVE-2026-40091 | authzed spicedb up to 1.51.0 log file

VDB-357646 · CVE-2026-40091 · GCVE-0-2026-40091 AUTHZED SPICEDB UP TO 1.51.0 LOG FILE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.1 $0-$5k 1.59+ Summaryinfo A vulnerability, which was classified as problematic, was found in authzed spicedb up to 1.51.0. This vulnerability affects unknown code. Executing a manipulation can lead to log file. This vulnerability is handled as CVE-2026-40091. It is possible to launch the attack on the local host. There is not any exploit available. You should upgrade the affected component. Detailsinfo A vulnerability has been found in authzed spicedb up to 1.51.0 and classified as problematic. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a log file vulnerability. The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. CVE summarizes: 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. The advisory is available at github.com. This vulnerability was named CVE-2026-40091 since 04/09/2026. The exploitation appears to be easy. Local access is required to approach this attack. The exploitation needs additional levels of successful authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project. Upgrading to version 1.51.1 eliminates this vulnerability. Productinfo Vendor authzed Name spicedb Version 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 1.48 1.49 1.50 1.51.0 Website Product: https://github.com/authzed/spicedb/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.1 VulDB Meta Temp Score: 4.1 VulDB Base Score: 2.3 VulDB Temp Score: 2.2 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.0 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Log file CWE: CWE-532 / CWE-200 / CWE-284 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: spicedb 1.51.1 Timelineinfo 04/09/2026 CVE reserved 04/15/2026 +6 days Advisory disclosed 04/15/2026 +0 days VulDB entry created 04/15/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-40091 (🔒) GCVE (CVE): GCVE-0-2026-40091 GCVE (VulDB): GCVE-100-357646 Entryinfo Created: 04/15/2026 07:15 Changes: 04/15/2026 07:15 (63) Complete: 🔍 Cache ID: 99:797:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸