CVE-2026-45091
CriticalSummary
In enterprise mode of the sealed-env library for Node.js and Java/Spring Boot, versions 0.1.0-alpha.1 through 0.1.0-alpha.3 embedded the operator's literal TOTP secret in the JWS payload of every minted unseal token. The JWS payload is base64-encoded JSON, but not encrypted.
Risk Assessment
Any party who could observe a minted token could decode the payload and extract the TOTP secret in plaintext, posing a serious security risk to the organization.
Recommendation
It is recommended to upgrade to version 0.1.0-alpha.4, where this vulnerability has been fixed.
Original NVD description (English source)
sealed-env is a cross-stack, zero-trust secret management library for Node.js and Java/Spring Boot. In sealed-env enterprise mode, versions 0.1.0-alpha.1 through 0.1.0-alpha.3 embedded the operator's literal TOTP secret in the JWS payload of every minted unseal token. JWS payload is base64-encoded JSON, NOT encrypted. Any party who could observe a minted token (CI build logs, container env dumps, kubectl describe pod, Sentry/Rollbar stack traces, log aggregators) could decode the payload and extract the TOTP secret in plaintext. This vulnerability is fixed in 0.1.0-alpha.4.

