CVE-2026-39833 Affecting spire-server package, versions <1.15.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (14th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-SPIRESERVER-16983122
  • published28 May 2026
  • disclosed22 May 2026

Introduced: 22 May 2026

NewCVE-2026-39833  (opens in a new tab)

How to fix?

Upgrade Chainguard spire-server to version 1.15.0-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream spire-server package and not the spire-server package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.