Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x3r2-fj3r-g5mv | sealed-env: TOTP secret embedded in unseal token payload (enterprise mode) |
Wed, 13 May 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Davidalmeidac
Davidalmeidac sealed-env |
|
| Vendors & Products |
Davidalmeidac
Davidalmeidac sealed-env |
Tue, 12 May 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 12 May 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | sealed-env: TOTP secret embedded in unseal token payload (enterprise mode) | |
| Weaknesses | CWE-200 CWE-522 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-12T14:39:10.904Z
Reserved: 2026-05-08T19:27:26.698Z
Link: CVE-2026-45091
Updated: 2026-05-12T14:39:04.937Z
Status : Deferred
Published: 2026-05-12T14:17:08.820
Modified: 2026-05-13T18:27:58.823
Link: CVE-2026-45091
No data.
OpenCVE Enrichment
Updated: 2026-05-13T10:38:55Z
Github GHSA