Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| davidalmeidac | sealed-env | < 0.1.0-alpha.4 | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
HORKimhab/CVE-2026-45091 ★ 0 · May 16, 2026
CVE-2026-45091
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | io.github.davidalmeidac:sealed-env-core | < 0.1.0-alpha.4 | 0.1.0-alpha.4 | GHSA-x3r2-fj3r-g5mv |
| npm | sealed-env | < 0.1.0-alpha.4 | 0.1.0-alpha.4 | GHSA-x3r2-fj3r-g5mv |