Davidalmeidac sealed-env
sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.1.0-alpha.4
Fixed in 0.1.0-alpha.4
Mitigation
Upgrade sealed-env to 0.1.0-alpha.4 or later.
References
- Vendor advisory github.com/davidalmeidac/sealed-env/security/a…
Timeline
Days relative to CVE publicationFirst public PoC 3.6 days after publication; not in CISA KEV. First PoC: HORKimhab/CVE-2026-45091 (created 16 May 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs · 1 not a PoC
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-45091 | 16 May 2026 +3.6 d | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Not a PoC 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-41901 | 23 May 2026 +11 d | 0 | Not a PoC · unrelated |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.