CVE-2026-45091: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in davidalmeidac sealed-env
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.
AI Analysis
Technical Summary
sealed-env versions 0.1.0-alpha.1 through 0.1.0-alpha.3 in enterprise mode embed the operator's literal TOTP secret within the JWS payload of unseal tokens. Since the JWS payload is base64-encoded JSON and not encrypted, anyone with access to these tokens can decode and retrieve the TOTP secret in plaintext. This constitutes an exposure of sensitive information (CWE-200) and improper protection of secrets (CWE-522). The issue is resolved in version 0.1.0-alpha.4.
Potential Impact
An attacker or unauthorized party who can observe minted unseal tokens can extract the operator's TOTP secret in plaintext, potentially compromising multi-factor authentication mechanisms relying on that secret. This exposure can lead to unauthorized access and compromise of the protected environment. The vulnerability does not affect availability but has high confidentiality and integrity impact.
Mitigation Recommendations
Upgrade sealed-env to version 0.1.0-alpha.4 or later, where the vulnerability is fixed. Until upgraded, avoid exposing minted unseal tokens in logs, environment dumps, or other observable outputs to prevent leakage of the TOTP secret. Patch status is confirmed fixed in 0.1.0-alpha.4.
CVE-2026-45091: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in davidalmeidac sealed-env
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
sealed-env versions 0.1.0-alpha.1 through 0.1.0-alpha.3 in enterprise mode embed the operator's literal TOTP secret within the JWS payload of unseal tokens. Since the JWS payload is base64-encoded JSON and not encrypted, anyone with access to these tokens can decode and retrieve the TOTP secret in plaintext. This constitutes an exposure of sensitive information (CWE-200) and improper protection of secrets (CWE-522). The issue is resolved in version 0.1.0-alpha.4.
Potential Impact
An attacker or unauthorized party who can observe minted unseal tokens can extract the operator's TOTP secret in plaintext, potentially compromising multi-factor authentication mechanisms relying on that secret. This exposure can lead to unauthorized access and compromise of the protected environment. The vulnerability does not affect availability but has high confidentiality and integrity impact.
Mitigation Recommendations
Upgrade sealed-env to version 0.1.0-alpha.4 or later, where the vulnerability is fixed. Until upgraded, avoid exposing minted unseal tokens in logs, environment dumps, or other observable outputs to prevent leakage of the TOTP secret. Patch status is confirmed fixed in 0.1.0-alpha.4.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T19:27:26.698Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0333e5cbff5d8610ef1d43
Added to database: 5/12/2026, 2:06:29 PM
Last enriched: 5/12/2026, 2:21:22 PM
Last updated: 5/12/2026, 6:14:47 PM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.