CVE-2026-40091: SpiceDB is an open source database system for creating and managing security-critical application permissions

Routine

MEDIUM 6.0UPGRADE

CVE-2026-40091 is a medium-severity flaw (CVSS 6.0) affecting spicedb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.0 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.2% (top 94%)
CISA exploited list	No
Weakness	CWE-532
Published	2026-04-15
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: authzed

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-15 04:17 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

authzed spicedb UPGRADE

Affected: >= 1.49.0 and < 1.51.1

Fixed in: 1.51.1

Safe to downgrade to: a release before 1.49.0

1. Check installed version

apt-cache policy spicedb || rpm -q spicedb || spicedb --version

2. UPGRADE to 1.51.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spicedb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spicedb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.49.0 (Debian / Ubuntu)

apt-cache madison spicedb sudo apt install spicedb=<VERSION_BEFORE_1.49.0> sudo apt-mark hold spicedb

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spicedb sudo dnf downgrade spicedb-<VERSION_BEFORE_1.49.0> sudo dnf versionlock add spicedb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40091?

spicedb: upgrade to 1.51.1. Exact commands for each OS are on this page.

Is CVE-2026-40091 being exploited?

CVE-2026-40091 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40091 affect?

CVE-2026-40091 affects spicedb. Severity is medium (CVSS 6.0). 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

How urgent is CVE-2026-40091?

Priority 22/100. No elevated risk signals yet.

References

← Back to latest CVEs