CVE-2026-45091 json
sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)
published 2026-05-12 5 mo ago modified 2026-10-26 13 d ago also GHSA-x3r2-fj3r-g5mv , EUVD-2026-29476
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm sealed-env 0.1.0-alpha.4
- maven io.github.davidalmeidac:sealed-env-core 0.1.0-alpha.4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | sealed-env | <0.1.0-alpha.4 |
0.1.0-alpha.4 |
| maven | io.github.davidalmeidac:sealed-env-core | <0.1.0-alpha.4 |
0.1.0-alpha.4 |
Affected products
- davidalmeidac sealed-env
Classification
References
Sources
- CVE List CVE-2026-45091
- GitHub Advisory GHSA-x3r2-fj3r-g5mv
- NVD CVE-2026-45091
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.