CVE-2026-40091 authzed CVE debrief

Who should care

Defenders managing SpiceDB installations, particularly those with log level set to info, should assess exposure and prioritize mitigation. This includes reviewing log configurations, upgrading to version 1.51.1, or changing the log level to warn or error. Affected operators, platforms, and security teams should review the issue and implement necessary controls to prevent unauthorized access to sensitive data.

Why it matters

CVE-2026-40091 exposes sensitive information in SpiceDB logs at log level info, requiring defenders to assess and mitigate the issue.

• Exposure of sensitive information in logs
• Potential for unauthorized access to sensitive data
• Need for log level adjustments or upgrades

Technical summary

SpiceDB versions 1.49.0 through 1.51.0 log the full datastore DSN, including plaintext passwords, at log level info during startup. This issue exposes sensitive information and can lead to potential unauthorized access. The issue is fixed in version 1.51.1, and defenders should prioritize upgrading or changing the log level to warn or error to mitigate the exposure of plaintext passwords in logs. SpiceDB is an open-source database system for managing security-critical application permissions, and defenders managing SpiceDB installations should assess exposure and prioritize mitigation.

Defensive priority

Defenders should prioritize upgrading to SpiceDB version 1.51.1 or changing the log level to warn or error to mitigate the exposure of plaintext passwords in logs.

Recommended defensive actions

• Upgrade to SpiceDB version 1.51.1
• Change the log level to warn or error
• Review and adjust logging configurations
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, affected versions, and fixed version. Vendor advisory and release notes are also available. SpiceDB versions 1.49.0 through 1.51.0 have a log level info issue that exposes sensitive information. Defenders should verify log configurations and prioritize mitigation. The issue is fixed in version 1.51.1.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.